misc: Split graphql definitions into two schemas #2603
Merged
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
rsempe
force-pushed
the
split-graphql-schemas
branch
4 times, most recently
from
e7db418
to
3dc4b3f
Compare
vincent-pochet
approved these changes
Sep 20, 2024
rsempe
force-pushed
the
split-graphql-schemas
branch
from
3dc4b3f
to
1037886
Compare
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.
The goal of this PR is to propose splitting the graphql definitions into two schemas.
One for the customer portal and one for the authenticated API.
As we'll add several resolvers / mutations for the customer portal, I think it could be better to put some isolation.
This first PR allows to keep the original implementation of the graphQL controller as it is... while introducing the 2 new endpoints.