langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Refactor/Chore] Clarify InvokeFrom.Published naming for published pipeline runs #21476

New Issue
Closed
opened 2026-02-21 20:12:45 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:12:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @laipz8200 on GitHub (Jan 6, 2026).

Originally assigned to: @laipz8200 on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

The InvokeFrom.Published enum name is ambiguous and makes it unclear that this source represents a published RAG pipeline run. This ambiguity makes it harder to understand invocation origins in pipeline-related flows.

Motivation

Clarifying the naming will make invocation sources explicit and reduce confusion when reading or reasoning about pipeline execution contexts.

Additional Context

This is purely a naming clarity request; the underlying value used in persisted data should remain unchanged for compatibility.

Originally created by @laipz8200 on GitHub (Jan 6, 2026). Originally assigned to: @laipz8200 on GitHub. ### Self Checks - [x] I have read the Contributing Guide and Language Policy. - [x] This is only for refactors or chores; if you would like to ask a question, please head to Discussions. - [x] I have searched for existing issues, including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Description The `InvokeFrom.Published` enum name is ambiguous and makes it unclear that this source represents a published RAG pipeline run. This ambiguity makes it harder to understand invocation origins in pipeline-related flows. ### Motivation Clarifying the naming will make invocation sources explicit and reduce confusion when reading or reasoning about pipeline execution contexts. ### Additional Context This is purely a naming clarity request; the underlying value used in persisted data should remain unchanged for compatibility.
yindo closed this issue 2026-02-21 20:12:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21476
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?