Use has_no_fields(true) in base types to silence warnings#290
Merged
mcelicalderon merged 1 commit intomasterfrom Apr 15, 2026
Merged
Use has_no_fields(true) in base types to silence warnings#290mcelicalderon merged 1 commit intomasterfrom
mcelicalderon merged 1 commit intomasterfrom
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
1 participant
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.
Using
has_no_fields(true)in the base types to suppress warnings. Apparently this will no longer be used in GraphQl 3.0. So the approach to userespond_to?is also future proof. We'll see what direction they take on 3.0Closes #283