From 1fa00fcf8fcbae51ae1c15e5896de5b35f4b1489 Mon Sep 17 00:00:00 2001 From: Gabriel Luiz Freitas Almeida Date: Mon, 31 Jul 2023 18:31:52 -0300 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20docs(custom-component.mdx):=20ad?= =?UTF-8?q?d=20note=20about=20custom=20components=20appearing=20in=20'Othe?= =?UTF-8?q?r'=20category=20if=20using=20a=20subdirectory=20not=20listed=20?= =?UTF-8?q?in=20config.yaml?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/docs/guidelines/custom-component.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/guidelines/custom-component.mdx b/docs/docs/guidelines/custom-component.mdx index 6f8187ccc..106a5f918 100644 --- a/docs/docs/guidelines/custom-component.mdx +++ b/docs/docs/guidelines/custom-component.mdx @@ -357,6 +357,8 @@ Create a folder that follows the same structural conventions as the [config.yaml Inside `custom_components`, you can create a Python file for each component. Similarly, any custom agents should be housed in an `agents` subdirectory. +If you use a subdirectory name that is not in our config.yaml file, your component will appear in an `Other` category in the sidebar. + Your structure should look something like this: ``` @@ -366,6 +368,8 @@ Your structure should look something like this: └── ... └── agents └── ... +└── my_agents <-- Other category + └── ... ``` ### Loading Custom Components