Skip to content

fix: replace null parents when resolving nested sections - #317

Open
fhgffy wants to merge 1 commit into
npm:mainfrom
fhgffy:fix-null-section-parents-20261011
Open

fhgffy wants to merge 1 commit into
npm:mainfrom
fhgffy:fix-null-section-parents-20261011

Conversation

@fhgffy

@fhgffy fhgffy commented Oct 10, 2026

Copy link
Copy Markdown

A null value used as the parent of a dotted section currently makes parse() throw. For example, a=null followed by [a.b] fails with Cannot set properties of null, while string and boolean parents are already replaced with section objects.

Treat null parents consistently with those other scalar values. The regression tests cover global and nested null parents, dotted keys, and preserving standalone null values.

Validation: npm test passes all six test files with 100% coverage, including ESLint and template checks. npm pack --dry-run --ignore-scripts also passes on Node 24.15.0. The new regression fails on the unchanged base.

@fhgffy
fhgffy requested a review from a team as a code owner October 10, 2026 20:13
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