-
Notifications
You must be signed in to change notification settings - Fork 288
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
fix(tasks): ensure task precedence is preserved during loading #1600
Conversation
given the test failure I think you removed the wrong one. That logic is so complicated I'm not sure though. |
4bf0dec
to
dbbab04
Compare
Lolol I see what the problem is: Created an e2e script with just the following:
This is the output:
And after removing
So I'll need to get e2e to ignore the legacy |
Soft-blocking this on #1612 since difficult to identify if current e2e suite is correctly failing or not. |
Related to this, I'm unsure if my strategy of using the fact there is a config file is even a good idea. I could see a user wanting to have tasks without a config file at all and the current solution doesn't allow for that. |
looking at this a bit deeper, I don't understand. If both ~/src/mise and ~/src/mise/e2e define a task, then the one in ~/src/mise/e2e should override what is in ~/src/mise. |
Yeah it doesn't really make sense so here is some debug Debug: Original
Removing last
Seems like the issue based on what the OP described is more due to the |
Closing in favor of #1625 |
I did some work in #1625 to refactor and improve this. A test is failing I need to sort out though. |
Summary
Fixes #1593
This initial call to
rev()
ensures that lower precedence config files are processed first and consequently their tasks and aliases are inserted into the resulting Map first and overridden by high precedence tasks.The additional call to
rev()
removed here inverted this behavior.