Resolve CamelCase prefixes in dotted Box lookups - #324
Open
Jerry-val wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When
camel_killer_boxandbox_dotsare enabled, an existing key such assomeKeyworks alone but fails insomeKey[0].innerKey. Withdefault_box=True, the same read can create an unintended branch.Resolve CamelCase aliases one path component at a time before traversal, preserving exact-key precedence. Regression tests cover nested dictionaries and lists, option combinations, unchanged data after reads, and exact literal keys.
Validation on Python 3.13: all 166 tests pass with Python source, compiled extensions, and the installed wheel. Black, mypy, distribution build, and Twine checks pass. The new regression tests fail before the fix.
Fixes #300.