One Settings class One Output File?

[hackermandh]

I've read the documentation, but it looks like you can't have a list of settings, where each settings class gets their own (markdown) file. There are no settings for this, correct?

If so, is there a chance to create this feature?

Context: I've created KafkaProducerSettings and KafkaConsumerSettings for kafka-python, which each share a KafkaBaseSettings class. These two settings classes are quite large, and I would like to have the generated markdown text be put into separate files, instead of both in a single markdown file.

[jag-k]

Hi! First of all, thanks for the interesting for this project!

For now I haven't this functionality, but it’ll be added soon. I can’t answer then exactly ('cause I have a lot of work), but this is a prototype of the future config:

[tool.pydantic_settings_export]
project_dir = "."
default_settings = ["my_app.settings:AppSettings"]  # can be empty list
env_file = ".env"

# Generate Markdown docs
[[tool.pydantic_settings_export.generators.markdown]]
paths = ["docs/settings.md"]
extend_settings = ["my_app.settings:AnotherAppSettings"]  # settings = default_settings + extend_settings

[[tool.pydantic_settings_export.generators.markdown]]
paths = ["docs/secrets.md"]
settings = ["my_app.secrets:Secrets"]  # will override `default_settings`

# Generate .env example
[[tool.pydantic_settings_export.generators.dotenv]]
paths = [".env.example"] # only default_settings will be here

If you have free time and want to help me with that, please feel welcome to make PR implementing this prototype!