Skip to content

Add env_nested_max_split setting #534

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 11, 2025
Merged

Conversation

gsakkis
Copy link
Contributor

@gsakkis gsakkis commented Feb 8, 2025

New setting to limit the parsing of nested env vars split by env_nested_delimiter up to a given nesting depth.

The main use case is to allow env_nested_delimiter='_' to work with fields that contain underscores, as proposed here.

Copy link
Contributor

@hyperlint-ai hyperlint-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The style guide flagged several spelling errors that seemed like false positives. We skipped posting inline suggestions for the following words:

  • [Ss]ubstring

@hramezani
Copy link
Member

Thanks @gsakkis for this PR.

I left some comments.

@gsakkis gsakkis changed the title Add env_nested_depth setting Add env_nested_max_split setting Feb 11, 2025
@hramezani hramezani merged commit ccf99b2 into pydantic:main Feb 11, 2025
23 checks passed
@gsakkis gsakkis deleted the env_nested_depth branch February 18, 2025 07:12
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.

None yet

2 participants