Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove limitation about order of inputs #126

Open
MarcelRobitaille opened this issue Dec 16, 2024 · 0 comments
Open

Remove limitation about order of inputs #126

MarcelRobitaille opened this issue Dec 16, 2024 · 0 comments

Comments

@MarcelRobitaille
Copy link
Collaborator

From the readme:

in the main task command the input variables should appear (left to right) in order of dependence

In theory, it should be possible to remove this limitation. In the variable resolver, when encountering an input that does not exist in the UserInputContext, it should be possible to execute that input in that moment. The arguments to CommandHandler are args (can be looked up through other means), userInputContext (we have it in the variable resolver), context (we get it from activate, so it could be piped through to the variable resolver), and subprocess (just an import).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant