Add .editorconfig to Core for specifying CA rules #17411
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.
Description of Change
For various reasons, the default code analysis rules have never been fully enforced in this repository. We would like to change that, but turning on all the rules for all projects at once is simply not an option with our current resources.
As an alternative, we can incrementally being enforcing these rules per-project, per-category, per-rule, and per-file via
.editorconfig
.While it's tempting to mass-fix violations for a particular rule or category, doing so may generate changes across dozens or even hundreds of files at once. This makes for confusing change histories and conflicts. Instead, we can fix violations in smaller, easily reviewed subsets and prevent future violations in those areas using
.editorconfig
. By doing this incrementally, we can ratchet up the level of enforcement until we can turn it on for entire projects.This change adds CA performance rule enforcement for Flex and PlatformTouchGraphicsView.