Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / pydantic/pydantic-settings issues and pull requests
#29 - Type error on BaseSettings config
Issue -
State: closed - Opened by pikeas over 3 years ago
- 5 comments
#28 - Interaction with `pydantic-next`
Issue -
State: closed - Opened by Kludex over 1 year ago
- 2 comments
Labels: question
#27 - BaseSettings: Environment variable is not loaded in nested model if defined in `Field()`
Issue -
State: closed - Opened by RafaelWO over 1 year ago
- 4 comments
#26 - Json Parse for Environment Variables in sub models does not work
Issue -
State: closed - Opened by chaimt over 1 year ago
- 3 comments
#25 - Ignore env_prefix if validation_alias is set
Pull Request -
State: closed - Opened by hramezani over 1 year ago
- 1 comment
#24 - Feature Request: Clearer errors with variable prefix included
Issue -
State: open - Opened by jambonrose over 4 years ago
- 4 comments
Labels: feature request
#23 - BaseSettings doesn't respect population by field name if env is present
Issue -
State: closed - Opened by RobertCraigie over 3 years ago
- 4 comments
#22 - Implement proper support for nested complex env values
Pull Request -
State: closed - Opened by hramezani over 1 year ago
- 2 comments
#21 - add "check" to ci
Pull Request -
State: closed - Opened by samuelcolvin over 1 year ago
- 1 comment
#20 - prepare release to use environments
Pull Request -
State: closed - Opened by samuelcolvin over 1 year ago
- 1 comment
#19 - Implemet protected namespaces
Issue -
State: closed - Opened by hramezani over 1 year ago
#18 - Adopt pydantic-settings docs for Pydantic V2
Pull Request -
State: closed - Opened by hramezani over 1 year ago
- 3 comments
#17 - Adopt pydantic-settings with Pydantic V2
Pull Request -
State: closed - Opened by hramezani over 1 year ago
- 2 comments
#16 - Move json parsing for complex field to pydantic
Issue -
State: closed - Opened by hramezani over 1 year ago
- 9 comments
#15 - Reimplement setting source classes
Pull Request -
State: closed - Opened by hramezani over 1 year ago
- 1 comment
#14 - env_prefix ignored when by pydantic.Field(env=...)
Issue -
State: closed - Opened by sileht over 1 year ago
- 1 comment
#13 - Support for Configuration file loading?
Issue -
State: closed - Opened by jordantshaw over 1 year ago
- 2 comments
#12 - Support `Field(env=...)` is submodels
Issue -
State: closed - Opened by samuelcolvin over 1 year ago
- 2 comments
#11 - Extra.Forbid is not applied when using BaseSettings with Config.env_file defined
Issue -
State: closed - Opened by jberthier-ma almost 2 years ago
- 7 comments
Labels: bug
#10 - [WIP] Improved source management
Pull Request -
State: closed - Opened by Geosynopsis almost 2 years ago
- 16 comments
#9 - The nested BaseSettings raise a validation error when its attribute is uppercase.
Issue -
State: closed - Opened by you-n-g almost 2 years ago
- 4 comments
Labels: bug
#8 - Move docs from Pydantic
Pull Request -
State: closed - Opened by hramezani almost 2 years ago
- 6 comments
#7 - BaseSettings does not propagate sources priority to BaseModel
Issue -
State: closed - Opened by superlevure over 2 years ago
- 5 comments
Labels: bug
#6 - Improved handling of setting sources
Issue -
State: closed - Opened by Geosynopsis almost 2 years ago
- 3 comments
#5 - Allow recursive env variables loading based on models jsonschema
Issue -
State: open - Opened by jooola about 2 years ago
- 5 comments
#4 - Pydantic BaseSettings should raise when .env file specified in `env_file` does not exist
Issue -
State: open - Opened by ralbertazzi about 2 years ago
- 4 comments
Labels: feature request
#3 - Support more than one directory for settings management
Issue -
State: closed - Opened by BrettMoan about 2 years ago
- 5 comments
Labels: feature request
#2 - Request for "with_attr_docs" feature
Issue -
State: closed - Opened by hmeine about 2 years ago
- 7 comments
#1 - Support alternative value resolution for BaseSettings
Issue -
State: closed - Opened by ofek about 2 years ago
- 4 comments