Repository navigation
Mention coverage scope in README.md - #1336
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Alfi Maulana <alfi.maulana.f@gmail.com>
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.
The Development section in
README.mdsays the project enforces 100% code coverage, but Vitest only counts files that a test file imports, sosrc/cli.tsandsrc/index.tsaren't part of that check. A reader taking the README at its word wouldn't know that some code isn't counted, or how to tell which.This adds that clause to the sentence, following threeal/rust-starter#192, and drops "on every run", which added nothing since the threshold always applies to the test command.
🤖 Generated with Claude Code