Map gql schema in all environments, so the UI/Nitro can use it #1290
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
C# Unit Tests98 tests 98 ✅ 5s ⏱️ Results for commit 0a071a9. |
hahn-kev
approved these changes
Nov 29, 2024
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.
Nitro falls back to introspection if the schema endpoint fails. That's why we previously had access to the schema in staging and prod even though we weren't mapping a schema endpoint.
With the upgrade to Hot Chocolate 14 schema introspection was disabled by default. So, the fallback stopped working.
There's no reason to hide the schema, so it ought to be mapped in all environments, so Nitro has it.