feat: allow including relationships by default#96
Merged
tobyzerner merged 3 commits intotobyzerner:mainfrom Mar 29, 2024
Merged
feat: allow including relationships by default#96tobyzerner merged 3 commits intotobyzerner:mainfrom
tobyzerner merged 3 commits intotobyzerner:mainfrom
Conversation
This file contains hidden or 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.
Hello 👋🏼,
This is a beautifully written package, it has been great working with 🙏🏼.
We have come across a use case where we need some relations included by default. We currently have to maintain a fork of our own due to some very unique edge case behavior that probably don't make sense having in the origin repository.
I am not sure if you would want to support default includes, but thought I'd send this your way just in case. Will probably push more for other changes that might make sense to contribute back as well.
This would work per endpoint: