fixed the order of generated metadata #608
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.
Description:
This package creates the metadata for events like this:
But when you export the metadata from hasura, the order is different:
This means you have to commit those changes every time if the order of exporting and generating metadata is not consistent. For example, if I change something in hasura and export the metadata and commit those changes, the next time I change my code, the order of the generated metadata will change and I have to commit those files again.
The manual solution is to make sure the order of generating/exporting metadata is the same, but that's annoying when you can fix this by changing one line of code.