Move flatErrors tests from fsharpqa #15251
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.
This should have been easier than it was.
It turns out that the --flaterrors option was only really enabled in one codepath, and for testing we don't use that one in testing, other than fsharpqa I suppose.
So this wires up setting the value in all of the others except: FSharpChecker.parseFile, because that one would mean an actual change to a public API.
I don't mind changing the API, but really we only noticed this in testing, and flatErrors is a "not advertised command line option" so it is probably safe enough to leave FSharpChecker alone.