Reuse TypegenConfig for SingleProjectConfigFile #4585
Closed
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.
There are some slight discrepancies between multi- and single-project configs at the moment, with some options only being configurable from multi-project configs, even though the compiler could read and support the same settings from both type of configs (examples:
use_import_type_syntax
,require_custom_scalar_types
, etc.).Changes
TypegenConfig
inSingleProjectConfigFile
and remove duplicated optionsno_future_proof_enums
fromFlowTypegenConfig
intoTypegenConfig
and removesFlowTypegenConfig
as it's now no longer requiredThis change is a breaking change, as the
custom_scalars
config option in the single-project config must now be specified ascustom_scalar_types
.