feat: Support disableMasking: true
option to disable fragment masking globally
#69
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.
This is a feature preview, and while we consider it stable and ready for production, we may consider changing it before the next
minor
release!Summary
This feature is enabled by configuring
gql.tada
with thedisableMasking: true
flag.When enabled, fragment masking is completely disabled, similar to if you added
@_unmask
to every single fragment.We consider this a necessary addition for some projects that would otherwise run into trouble when having a “document cache” where query data is modified as a whole, which is a bad match for fragment masking.
Set of changes
disableMasking: flag
forcingmasked: false
on fragment references