Config-style: control over forcing vs optimization #3961
Merged
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.
Currently, the
runner.optimizer
parameters always force config-style formatting whennewlines.configStyle.xxxSite.prefer
is true, even though they were intended primarily to affect the route search.On the other hand, there could be cases when a user wouldn't enable the
newlines.configStyle.xxxSite.prefer
flag for regular operation (for instance, it makes no sense fornewlines.source=fold/unfold
) but would still be interested in forcing config-style.Therefore, let's add the sibling
xxxSite.forceConfigStyleIfOptimized
flag to decide when to force.Helps with #3954.