feat: moving away from juniper and sea-orm #88
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.
PR to move away from both juniper and sea-orm.
Juniper has been a thorn in my side for quite a while due to it lagging behind in features that asnyc-graphql now provides. It's a similar story with seaORM, where I feel like I'm trying to fight with the ORM to do things that I can do easily in SQL.
And so, I finally decided to bite the bullet and start switching.
I'd like to finish this before trying to resolve [nolink] #85 & #86 as migrating would help with adding those tremendously.
Checklist: