Fix/decoder correctness (2/8) #43
Open
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.
Linked Issue
Closes #
Description
Fix decoder correctness for keys, delimiters, path expansion, numeric rules, and option wiring. This allows keyword keys in key context, enforces ASCII unquoted key rules in strict mode, fixes delimiter scoping in nested arrays, preserves quoted dotted field names, and wires coerce_types and delimiter options correctly. It also adjusts handling for negative leading-zero numbers, unquoted tabs, and multiple internal spaces. This is PR 2 of 8 in the intended sequence (1-8).
Type of Change
Changes Made
SPEC Compliance
Testing
Tests run: cargo test
Pre-submission Checklist
Breaking Changes
Migration path:
Additional Context
Branch: fix/decoder-correctness
Intended PR order: 1-8 (this is PR 2 of 8)