Skip to content
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

Automatically generate docs from component definitions #345

Open
langestefan opened this issue Nov 25, 2024 · 0 comments
Open

Automatically generate docs from component definitions #345

langestefan opened this issue Nov 25, 2024 · 0 comments

Comments

@langestefan
Copy link
Contributor

langestefan commented Nov 25, 2024

I've been going through the code / docs quite a bit these past few days, because I'm adding some components I need.

Is your feature request related to a problem? Please describe.

Some components have no documentation (HeatingResistor for example), some components have incomplete documentation. Fields like states and connectors are manually typed and there is no standardization in how those parts of the docs are formatted. This makes it more difficult to find what you need.

Describe the solution you’d like

Instead of manually putting docstrings at the top of component definitions I suggest we directly generate documentation from the fields inside @mtkmodel. In particular description, bounds, guess, unit and any other fields that are available from the metadata: Symbolic Metadata. This avoids the need to type everything twice. We can still have a docstring at the top with a broader description. The fields can be automatically generated and put in a table for example.

This is an example of what I would like to achieve: https://developers.home-assistant.io/docs/core/entity/number

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

No branches or pull requests

1 participant