Skip to content

test(conformance): a newline between a key and its { is no open question - #21

Merged
lejmr merged 2 commits into
mainfrom
agent/newline-brace
Oct 19, 2026
Merged

lejmr merged 2 commits into
mainfrom
agent/newline-brace

Conversation

@lejmr

@lejmr lejmr commented Oct 19, 2026

Copy link
Copy Markdown
Owner

key-value-separator/006 (foo then { a = 1 } on the next line) was an open question. It is not one: the newline is whitespace between the key and the {, as JSON allows whitespace before :, and there is no other reading, since a key cannot start with {. Every parser in the table accepts it; hocon-rs rejecting it is its bug.

  • The case loses review, its why says the above.
  • Every report re-measured: each gains this one case and nothing else changed (zig-hocon 443/445 against the spec, Java 443/445 against itself, …).
  • Open questions left: 2.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CbBo1aotFTDLY2gery7qYD

lejmr and others added 2 commits October 19, 2026 17:33
`foo` then `{ a = 1 }` on the next line is the key followed by `{`, with
whitespace between, as JSON allows whitespace before `:`. No other reading
exists, since a key cannot start with `{`. Every parser in the table reads it
so; hocon-rs rejecting it is its bug, not a gap in the spec. The case is an
ordinary one now, and every report gains it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CbBo1aotFTDLY2gery7qYD
@lejmr
lejmr force-pushed the agent/newline-brace branch from 34e49aa to 718f084 Compare October 19, 2026 16:08
@lejmr
lejmr merged commit 718f084 into main Oct 19, 2026
42 checks passed
@lejmr
lejmr deleted the agent/newline-brace branch October 19, 2026 16:15
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