Repository navigation
fix(distribution): verify quoted native input paths - #16
Merged
Merged
Conversation
Contributor
Contribution progressSource: Selected validations:
Applicable consumers are synchronized on their development branches and the staging sites. Releases are published from main; the Release row follows them. |
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.
Use platform-native quoted paths when verifying unreadable and oversized input diagnostics. Redact both plain and JSON-escaped sandbox paths while retaining the exact filename, diagnostic code and failure status.
bun run checkpassed: 306 tests. The Windows path regression covers both plain and quoted diagnostics; existing refusal tests continue to reject wrong codes, exit statuses, headlines and successful verdicts.