Fix bug with priorities not getting saved #119
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was working with a repo that has both a
.env
and a.env.development.local
today and couldn't figure out why calling.load()
or.config()
was giving me values from.env
every time until I deleted the file. Turns out the code that walks the priorities wasn't working – the current priority object was never set, so the file order is all that was determining what was getting picked. This edit fixed it for me locally.