Repository navigation
docs: clarify excludeFiles replacement behavior - #217
Merged
Merged
Conversation
Document full array replacement in both READMEs. Lock the custom and empty array behavior in configuration tests.
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
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.
What changed
excludeFilesreplacement in both READMEs.**/dist/**.getLintConfig().Why
A configured array already replaces the defaults.
The docs now state this behavior.
The tests keep this contract visible during future changes.
Verification
npm test -- --runInBand __tests__/configure.spec.ts: 34 tests passed.npm run lint: passed.git diff --check: passed.No logs or user data are included.
Closes #216