Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: avoid unrelated schemaOverrides when building definition for single type #589

Merged

Conversation

lundibundi
Copy link
Contributor

Please:

  • Make your pull request atomic, fixing one issue at a time unless there are many relevant issues that cannot be decoupled.
  • Provide a test case & update the documentation in the Readme.md

I want to use setSchemaOverride to override some types and then generate separate schema files per type with getSchemaForSymbol. Current implementation adds all overrides to each schema even if they are not used. This PR removes that behavior by default and adds an option includeAllOverrides to return it.
The includeAllOverrides is also enabled by default when generating schema for whole program.

@domoritz domoritz merged commit 0a963ca into YousefED:master Feb 14, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants