fix: add docs links to dingtalk wecom and qq setup dialogs#943
Merged
fix: add docs links to dingtalk wecom and qq setup dialogs#943
Conversation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
anthhub
approved these changes
Apr 8, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add bottom-of-dialog docs links for the DingTalk, WeCom, and QQ channel setup dialogs.
Why
These three channel setup dialogs did not expose the Nexu setup guides at the bottom of the popup, unlike the existing channel connect modal pattern. Adding the links makes the setup path consistent and gives users direct access to the docs.
How
Add a docs URL constant to each setup view and render a bottom help link using the existing
modal.viewDocsi18n copy.Affected areas
Checklist
pnpm typecheckpassespnpm lintpassespnpm testpassespnpm generate-typesrun (if API routes/schemas changed)anytypes introduced (useunknownwith narrowing)Notes for reviewers
pnpm testwas not run because this is a small UI-only change with no logic or API surface changes.