chore: adopt the revised canonical .editorconfig (Standards §5.2) - #27
Merged
Conversation
The canonical .editorconfig in NextIteration.Standards was revised (templates update, standards #15): it moves to a deliberate allow-list of gated style rules with no blanket dotnet_analyzer_diagnostic.severity, and fixes the private-field naming rule that previously demanded _camelCase for PascalCase constants. §5.2 requires this file to be the canonical copy verbatim. EnforceCodeStyleInBuild stays OFF per §1.2.1 (blocked estate-wide until the per-rule gate/advisory split is decided), so the IDE* :warning severities are advisory at build time. The one build-affecting change is CS1591 moving from silent to warning: a missing XML doc on a public member is now a hard error under TreatWarningsAsErrors. The public surface is already fully documented, so Release build is clean (0 warnings). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
StuartMeeks
force-pushed
the
chore/adopt-canonical-editorconfig
branch
from
August 21, 2026 05:22
aed8adc to
b4e6ded
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of the standards recheck ahead of 1.0.0. NextIteration.Standards revised the canonical
.editorconfig(standards #15); §5.2 requires this repo to carry it verbatim, and the adoption audit notes all five repos fail §5.2 on this file until they take the update.What changes
.editorconfigreplaced with the canonical template, byte-for-byte.dotnet_analyzer_diagnostic.severity— so a style rule a future SDK ships can't silently auto-gate the build._camelCaseforPascalCaseconstants.Build safety
EnforceCodeStyleInBuildstays OFF per §1.2.1 (blocked estate-wide), so theIDE*:warningrules stay advisory at build time — no mass reformatting is forced.CS1591silent→warning: a missing XML doc on a public member is now a hard error underTreatWarningsAsErrors. The public surface is already fully documented, so Release build is clean (0 warnings).Not in this PR
analyzerequired check +code_scanningrule) are a repo-settings change, handled separately.🤖 Generated with Claude Code