Path Specifications
File paths in the manifest or any YAML file follow two rules, depending on the file type:- Multimedia files such as images and videos (for example, the plugin’s
icon) go in the_assetsfolder under the plugin’s root directory. - Regular text files, such as
.pyor.yamlcode files, are referenced by their absolute path within the plugin project.
Common Structures
Some data structures are shared between tools, models, and Endpoints. They are defined here.I18nObject
I18nObject is an internationalization structure that conforms to the IETF BCP 47 standard. Four languages are supported:
ProviderConfig
ProviderConfig is a common provider form structure used by both Tool and Endpoint.
Display labels, following the IETF BCP 47 standard.
Help document link label, following IETF BCP 47.
Placeholder text in multiple languages, following IETF BCP 47.
ProviderConfigOption (object)
Option display label, following IETF BCP 47.
ProviderConfigType (string)
ProviderConfigScope (string)
Whentype is model-selector:
When type is app-selector:
When type is tool-selector:
ModelConfig
Model type enumeration; see Model Design Rules.
NodeResponse
ToolSelector
Related Resources
- Basic Concepts of Plugin Development—an overview of Dify plugin development
- Developer Cheatsheet—quick reference for common commands and concepts
- Tool Plugin Development Details—defining plugin information and the tool plugin development process
- Model Design Rules—standards for model configuration