fix(web): hide wallet entry in profile dropdown when wallet module disabled

[feitianbubu]

📝 变更描述 / Description

右上角用户下拉菜单里的「钱包」入口是无条件渲染的，没有读取侧边栏模块配置。所以当管理员在系统设置里关闭 personal/topup(钱包)模块后,侧边栏的钱包入口已隐藏,下拉菜单里却仍然显示。

本 PR 让下拉菜单复用侧边栏已有的模块可见性判定:新增 useIsSidebarModuleVisible(url)(复用现有的 parseSidebarConfig / parseUserSidebarConfig / isModuleEnabled),钱包菜单项仅在 /wallet 模块可见时才渲染。这样下拉菜单与侧边栏走完全相同的 admin × user 两层规则,关闭钱包显示后两处一致隐藏。

🚀 变更类型 / Type of change

• 🐛 Bug 修复 (Bug fix)

🔗 关联任务 / Related Issue

• Closes 系统设置中关闭钱包显示后，右上角用户下拉还会显示钱包 #5696

✅ 提交前检查项 / Checklist

• 人工确认: 我已亲自整理并撰写此描述。
• 非重复提交: 已搜索现有 Issues 与 PRs,确认不是重复提交。
• Bug fix 说明: 已关联对应 Issue 系统设置中关闭钱包显示后，右上角用户下拉还会显示钱包 #5696。
• 变更理解: 已理解这些更改的工作原理及可能影响。
• 范围聚焦: 本 PR 仅包含此项修复,无无关改动。
• 本地验证: 已本地复现该 bug,并验证修复后下拉菜单随模块开关一致隐藏;tsc --noEmit 通过。
• 安全合规: 无敏感凭据,符合项目代码规范。

📸 运行证明 / Proof of Work

关闭「钱包」模块前:下拉菜单显示 个人资料 / 钱包 / 系统设置 / 登出。
关闭后:下拉菜单显示 个人资料 / 系统设置 / 登出,与侧边栏一致(钱包入口隐藏)。
修复前:

修复后:

[coderabbitai]

Walkthrough

Adds a new useIsSidebarModuleVisible(url) hook to use-sidebar-config.ts that derives admin and user sidebar configs and returns isModuleEnabled for a given route. ProfileDropdown uses this hook to conditionally render the Wallet menu item only when the /wallet module is enabled.

Changes

Wallet visibility in profile dropdown

Layer / File(s)	Summary
useIsSidebarModuleVisible hook web/default/src/hooks/use-sidebar-config.ts	Exports a new hook that reads status.SidebarModulesAdmin and auth.user permissions/sidebar config, then returns isModuleEnabled(url, adminConfig, userConfig) for the provided route.
Conditional Wallet menu item web/default/src/components/profile-dropdown.tsx	Imports and calls useIsSidebarModuleVisible('/wallet') to derive isWalletVisible, then wraps the Wallet DropdownMenuItem in a conditional render gated on that value.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐇 Hippity hop, the wallet hides away,
When the sidebar config says "not today."
A hook checks the settings, admin first,
Then user perms — no menu burst!
Only show the coins when truly allowed,
This bunny keeps the dropdown uncluttered and proud. 🪙

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: hiding the wallet entry when the wallet module is disabled.
Linked Issues check	✅ Passed	The code makes the dropdown respect sidebar visibility rules, which directly addresses issue #5696.
Out of Scope Changes check	✅ Passed	The added hook and dropdown condition are directly related to the reported wallet visibility bug.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

web/default/src/hooks/use-sidebar-config.ts (1)

317-330: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Optional: deduplicate sidebar config derivation.

Lines 321-327 repeat the admin/user config derivation already in useSidebarConfig (lines 278-296). Consider extracting a small internal hook (e.g. useResolvedSidebarConfig() returning { adminConfig, userConfig }) and reusing it in both places so the user-permission/override logic stays in one spot.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@web/default/src/hooks/use-sidebar-config.ts` around lines 317 - 330, The
admin/user sidebar config resolution is duplicated between
useIsSidebarModuleVisible and useSidebarConfig, so centralize that logic in a
small internal helper or hook like useResolvedSidebarConfig() that returns
adminConfig and userConfig. Reuse it from both useIsSidebarModuleVisible and
useSidebarConfig so the permissions and override handling stay consistent in one
place.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@web/default/src/hooks/use-sidebar-config.ts`:
- Around line 317-330: The admin/user sidebar config resolution is duplicated
between useIsSidebarModuleVisible and useSidebarConfig, so centralize that logic
in a small internal helper or hook like useResolvedSidebarConfig() that returns
adminConfig and userConfig. Reuse it from both useIsSidebarModuleVisible and
useSidebarConfig so the permissions and override handling stay consistent in one
place.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 01d1707a-41ac-4eab-8139-e4080661b470

📥 Commits

Reviewing files that changed from the base of the PR and between 72b3f34 and e9935f9.

📒 Files selected for processing (2)

• web/default/src/components/profile-dropdown.tsx
• web/default/src/hooks/use-sidebar-config.ts