fix: made sure fixtures are loaded in the correct order #604
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For complicated reasons I had to create yet another clone of the project (counter is on 4 now lol). I thought, let's use the new fancy load-fixtures command!
Only to discover that it had some issues with load-order. It tried to load registrationkinds before registrations, but registrationkinds depends on registrations. So, this PR addresses that issue:
os.listdirreturns the list in an arbitrary orderingtasks, to ensure one is loaded before the otherThe other fixtures loaded fine without the extra filename ordering, so I left them as-is