Skip to content

fix: allow periods in configuration field labels - #154

Open
Shubham-Padkonde wants to merge 1 commit into
1Password:mainfrom
Shubham-Padkonde:fix/dotted-field-labels
Open

Shubham-Padkonde wants to merge 1 commit into
1Password:mainfrom
Shubham-Padkonde:fix/dotted-field-labels

Conversation

@Shubham-Padkonde

Copy link
Copy Markdown

load and load_dict currently reject field labels containing periods because the entire opfield is split into components and exactly two are required. Split only at the first period: it separates the section from the field label, while remaining periods belong to the label. This supports the email-address label reported in #44, including fields outside a section.

The docstrings describe this interpretation. Four HTTP-backed regressions cover both entry points with and without a section; all four fail before the fix and pass afterward. All 56 tests pass, and git diff --check passes. Section labels containing periods remain outside the existing path syntax; this change does not add an escape syntax.

Fixes #44.

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.

load_dict fails when looking up keys with periods in them

1 participant