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 web/service hooks to use service wrappers #21406

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

Originally created by @lyzno1 on GitHub (Jan 2, 2026).

Goal

Standardize web/service to follow the convention:

  • use-* files expose TanStack Query hooks only.
  • non-use-* files expose pure request wrappers only.

Scope

Refactor existing web/service/use-* hooks to call the service-layer wrappers instead of calling @/service/base directly, and add missing wrappers where needed.

Tasks

  • Ensure each use-* hook delegates to a non-hook service function.
  • Add/extend service modules under web/service/* for missing endpoints.
  • Align types and request signatures (datasets/pipeline/plugins/tools/workflow/common).
  • Keep mocks/tests in sync with the import changes.

Done Criteria

All web/service/use-* hooks depend on web/service/* wrappers, with no direct @/service/base calls in those hooks.

Originally created by @lyzno1 on GitHub (Jan 2, 2026). ### Goal Standardize `web/service` to follow the convention: - `use-*` files expose TanStack Query hooks only. - non-`use-*` files expose pure request wrappers only. ### Scope Refactor existing `web/service/use-*` hooks to call the service-layer wrappers instead of calling `@/service/base` directly, and add missing wrappers where needed. ### Tasks - Ensure each `use-*` hook delegates to a non-hook service function. - Add/extend service modules under `web/service/*` for missing endpoints. - Align types and request signatures (datasets/pipeline/plugins/tools/workflow/common). - Keep mocks/tests in sync with the import changes. ### Done Criteria All `web/service/use-*` hooks depend on `web/service/*` wrappers, with no direct `@/service/base` calls in those hooks.
yindo closed this issue 2026-02-21 20:12:25 -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#21406
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?