This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
fix(Graphql): Ensure GraphQL hasInverse works #34
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In the past, hasInverse in GraphQL had been avoiding the use of reverse directive available at the core. After a careful review, I decided it's best to remove the
@reversedirective from the core. It was adding a bunch of complexity, which was unwarranted. The same can be achieved by adding edges in both the directions at the GraphQL layer.In this PR, I've added support for hasInverse back after the rewrite of #32 ( 9b9d56 ).
BREAKING: This change removes
@reversedirective from Outserv core.Fixes #35 .
This change is