fix(parser): reject invalid zippy output mappings - #2112
Merged
Conversation
Contributor
Author
|
@jtroo We'd appreciate it if you could take a look at this pull request when you have a chance. |
jtroo
approved these changes
Jul 15, 2026
Owner
|
Thanks! |
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.
Summary
Reject malformed
no-eraseandsingle-outputzippychord mappings with parser errors.Previously, mappings without required output values indexed an empty list and panicked during configuration validation. A
no-erasemapping with extra values was also accepted instead of rejected.Validation
cargo test --all --no-default-featurescargo test --allcargo clippy --all --no-default-features -- -D warningscargo clippy --all -- -D warningscargo fmt --all --check