Consume shared quality configuration - #4
Merged
Merged
Conversation
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.
Consume the formally merged shared dprint/ESLint configuration at
c63c2e8c2ba7e11502934a52ad2ce3734e804cdcinstead of repeating organization settings. Retain owner language/framework configuration, precise generated/vendor exclusions and existing product checks.Full-source ESLint currently has zero errors and runs as a blocking CI step, alongside the native configuration-consumption audit.
Validation: native dprint resolved settings are unchanged; formatting and final installed configuration/coverage audit pass. Existing dependency-lock entries remain unchanged; the shared Git dependency and its npm-generated integrity are locked. The portal check passed.
The shared audit rejects formatter-covered JS/TS without an ESLint configuration, so introducing an unsupported language fails instead of silently escaping the rule. The standard new-file gate was verified with a real Git diff: a new 1000-line file passes and a new 1001-line file fails, while an edited historical oversized file stays outside that gate.