Clarify external packages must have source code published (#2172)

* Clarify external packages must have source code published

* Improve language

* Improve language

* Update docs/api_lib_index.md

Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>

* Update docs/creating_component_code_review.md

* Update docs/api_lib_index.md

* Update docs/api_lib_index.md

---------

Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
This commit is contained in:
Erik Montnemery
2024-08-27 14:25:29 +02:00
committed by GitHub
parent 613d1190f3
commit adb09ecf85
5 changed files with 17 additions and 7 deletions

View File

@@ -16,6 +16,6 @@ We have created two example integrations that should give you a look at how this
One Home Assistant rule is that the integration should never interface directly with devices. Instead, it should interact with a third-party Python 3 library. This way, Home Assistant can share code with the Python community and keep the project maintainable.
Once you have your Python library ready and published to PyPI, add it to the [manifest](creating_integration_manifest.md). It will now be time to implement the Entity base class that is provided by the integration that you are creating a platform for.
Once you have your Python library [ready and published to PyPI](api_lib_index.md), add it to the [manifest](creating_integration_manifest.md). It will now be time to implement the Entity base class that is provided by the integration that you are creating a platform for.
Find your integration at the [entity index](core/entity.md) to see what methods and properties are available to implement.