-
Notifications
You must be signed in to change notification settings - Fork 361
Restore the api-extension-related docs #663
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request restores API extension documentation that was previously available on the old docs site. The changes add comprehensive documentation for API extensions in Dify across three languages (English, Chinese, and Japanese).
Changes:
- Added API extension documentation covering overview, external data tools, moderation functionality, and Cloudflare Workers deployment
- Updated workspace description in Chinese version from English to Chinese translation
- Integrated API extension section into the documentation navigation structure across all three language versions
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| zh/use-dify/workspace/readme.mdx | Translated workspace description from English to Chinese |
| zh/use-dify/workspace/api-extension/*.mdx | Added Chinese documentation for API extensions (overview, external data tool, moderation, Cloudflare deployment) |
| ja/use-dify/workspace/api-extension/*.mdx | Added Japanese documentation for API extensions with same structure as Chinese version |
| en/use-dify/workspace/api-extension/*.mdx | Added English documentation for API extensions with same structure |
| docs.json | Updated navigation to include new API extension documentation section for all three languages |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
zh/use-dify/workspace/api-extension/moderation-api-extension.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| * `app.moderation.input` 终端用户输入的内容审查扩展点 | ||
| * 用于审查终端用户传入的变量内容以及对话型应用中对话的输入内容。 | ||
| * `app.moderation.output`LLM 输出的内容审查扩展点 |
Copilot
AI
Jan 16, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing space between the closing backtick and 'LLM'. There should be a space after the backtick for consistent formatting. Compare with line 9 which correctly has a space.
| * `app.moderation.output`LLM 输出的内容审查扩展点 | |
| * `app.moderation.output` LLM 输出的内容审查扩展点 |
|  | ||
|
|
Copilot
AI
Jan 16, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Japanese documentation includes an additional image (line 53) that is not present in the English (line 51) or Chinese (line 51) versions. This creates inconsistency across language versions. Either add the image to all versions or remove it from the Japanese version for consistency.
|  |
| } | ||
| ``` | ||
|
|
||
| #### API Response <a href="#usercontentapi-fan-hui-1" id="usercontentapi-fan-hui-1"></a> |
Copilot
AI
Jan 16, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The anchor tag contains Chinese pinyin 'api-fan-hui-1' (meaning 'API return'). This should either be removed or use English identifiers for consistency with the English documentation.
| #### API Response <a href="#usercontentapi-fan-hui-1" id="usercontentapi-fan-hui-1"></a> | |
| #### API Response <a href="#usercontent-api-response-1" id="usercontent-api-response-1"></a> |
2b0efb8 to
db0dbeb
Compare
Restore API extension content from the old docs site.