Inherit the knowledge pipeline template icon when creating a knowledge base
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- frontend
调研方向
The issue names no files or tests; start by tracing the Knowledge Pipeline template creation flow and the existing knowledge-base icon-editing UI. Confirm how the selected template icon and the knowledge-base icon are represented, then verify that creation uses the template icon while later manual icon changes remain possible.
由索引模型根据 Issue 内容生成。
描述
Self Checks
- I have read the Contributing Guide and Language Policy.
- I have searched for existing issues search for existing issues, including closed ones.
- I confirm that I am using English to submit this report, otherwise it will be closed.
- Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
When a knowledge base is created from a Knowledge Pipeline template, its icon currently falls back to the generic default knowledge-base icon instead of using the icon shown on the selected template.
For example, the Complex PDF with Images & Tables template has a distinctive PDF-related icon on the template selection page. After creating a knowledge base from that template, the resulting knowledge base displays the generic orange book icon.
This makes it harder to identify which template was used to build a knowledge base, especially when a workspace contains multiple knowledge bases created from different pipeline templates.
2. Additional context or comments
Expected behavior
- A knowledge base created from a Knowledge Pipeline template should initially inherit that template's icon.
- The inherited icon should only be the default at creation time.
- Users should still be able to change the knowledge base icon afterward through the existing icon-editing UI.
This would preserve visual context from the template selection flow and make template-based knowledge bases easier to recognize and manage.
3. Can you help us with this feature?
- I am interested in contributing to this feature.
- 主要语言
- TypeScript
- 星标
- 157k
- 派生
- 24.7k
- 平均合并
- 22 小时 32 分钟
- 30 天内合并 PR
- 611
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
langgenius/dify 的其他 Issue
-
Annotation Reply: a stored score threshold of 0.0 is silently replaced with 1, disabling the feature 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42639 · 1 条评论 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 70/100
langgenius/dify#42468 · 1 条评论 · 1 个 reaction ·
-
🐞 bug
难度 2/5 1-3 小时 新手友好度 86/100
langgenius/dify#42446 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42355 · 1 条评论 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42350 · 1 条评论 · 1 个 reaction ·
相似的 Issue
-
calcite-components needs triage refactor
难度 2/5 1-3 小时 新手友好度 75/100
Esri/calcite-design-system#15203 ·
-
难度 2/5 1-3 小时 新手友好度 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 95/100
-
难度 2/5 1-3 小时 新手友好度 78/100
Automattic/studio#4908 ·
-
难度 2/5 1-3 小时 新手友好度 90/100