fix: avoid unrelated schemaOverrides when building definition for single type #589
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.
Please:
Readme.md
I want to use
setSchemaOverride
to override some types and then generate separate schema files per type withgetSchemaForSymbol
. Current implementation adds all overrides to each schema even if they are not used. This PR removes that behavior by default and adds an optionincludeAllOverrides
to return it.The
includeAllOverrides
is also enabled by default when generating schema for whole program.