From 8ececbe8ae861ea8d5444e13f847b0a847be845c Mon Sep 17 00:00:00 2001 From: Classic298 <27028174+Classic298@users.noreply.github.com> Date: Sat, 12 Apr 2025 11:07:35 +0200 Subject: [PATCH] Update development.mdx --- docs/features/plugin/tools/development.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/plugin/tools/development.mdx b/docs/features/plugin/tools/development.mdx index 6f2ad256..e779cdd3 100644 --- a/docs/features/plugin/tools/development.mdx +++ b/docs/features/plugin/tools/development.mdx @@ -50,7 +50,7 @@ class Tools: ``` ### Type Hints -Each tool must have type hints for arguments. As of version OpenWebUI version 0.4.3, the types may also be nested, such as `queries_and_docs: list[tuple[str, int]]`. Those type hints are used to generate the JSON schema that is sent to the model. Tools without type hints will work with a lot less consistency. +Each tool must have type hints for arguments. As of version Open WebUI version 0.4.3, the types may also be nested, such as `queries_and_docs: list[tuple[str, int]]`. Those type hints are used to generate the JSON schema that is sent to the model. Tools without type hints will work with a lot less consistency. ### Valves and UserValves - (optional, but HIGHLY encouraged) @@ -314,7 +314,7 @@ In the Tools definition metadata you can specify custom packages. When you click Keep in mind that as pip is used in the same process as Open-WebUI, the UI will be completely unresponsive during the installation. -No measures are taken to handle package conflicts with Open-WebUI's requirements. That means that specifying requirements can break OpenWebUI if you're not careful. You might be able to work around this by specifying `open-webui` itself as a requirement. +No measures are taken to handle package conflicts with Open-WebUI's requirements. That means that specifying requirements can break Open WebUI if you're not careful. You might be able to work around this by specifying `open-webui` itself as a requirement.