Skip to content

fix: decode escaped dots in nested section names - #314

Open
Imkkey wants to merge 1 commit into
npm:mainfrom
Imkkey:fix/escaped-nested-section-dots
Open

Imkkey wants to merge 1 commit into
npm:mainfrom
Imkkey:fix/escaped-nested-section-dots

Conversation

@Imkkey

@Imkkey Imkkey commented Oct 1, 2026 •

Copy link
Copy Markdown

References

Fixes #22. Nested section names with escaped dots don’t round-trip correctly. This fixes parent key decoding and adds regression tests for nesting and literal-dot collisions.
npm test passes on Node 24, including lint. The test suite also passes on Node 22 and 26, with 100% coverage.

@Imkkey
Imkkey requested a review from a team as a code owner October 1, 2026 18:46
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.

dots aren't decoded in deeply nested sections

1 participant