Skip to content

docs: clarify where implementations read 4.1 differently - #65

Merged
johannschopplich merged 23 commits into
mainfrom
docs/spec-4.1.3
Oct 5, 2026
Merged

johannschopplich merged 23 commits into
mainfrom
docs/spec-4.1.3

Conversation

@johannschopplich

@johannschopplich johannschopplich commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Wording fixes and fixtures for places where the ports read 4.1 differently. Every change pins what the 4.1 text already says, so this is a 4.1.x patch with no behavior change.

  • Contradictions – two root scalars are an error in any mode in §5 too, and neither the non-strict leniency for trailing content nor the skip for over-indented lines covers scalar lines.
  • Gaps – surrogate escapes are rejected in pairs too, any other array in list form nests as a list, spaces may separate a quoted key from its colon, field entries are trimmed, and only one CR before the line end belongs to the terminator.
  • Fixtures – 29 cases, one or more per change, plus rules that had no fixture yet. The lone-CR case from test: cover the fixture gaps found in the port reviews #63 goes, since the double-CR case covers it.

Stacked on #63. Two new cases fail the reference until toon-format/toon#355 lands: "a" : 1 and a bare token after a root array in non-strict mode.

@johannschopplich
johannschopplich merged commit 9720265 into main Oct 5, 2026
1 check passed
@johannschopplich
johannschopplich deleted the docs/spec-4.1.3 branch October 5, 2026 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant