为匿名和登录用户设置基于组的细粒度权限

martin · 2026 年7 月 16 日 03:48

martin:

以群组侧边栏菜单为例，我认为应该以相同的方式实现，因此配置中会有如下内容：
groups:
  type: groups
  required: true
  resolve_group_memberships: true
  validations:
    max: 20
然后在客户端，groups 将变为布尔值 user_in_groups。

我已在下面的 PR 中实现了此功能：

github.com/discourse/discourse

DEV: Add resolve_group_membership for theme object settings of group type (#41756)

main ← dev/resolve-group-membership-theme-object-group

merged 12:19AM - 17 Jul 26 UTC

martin-brennan

+601 -14

Followup 7e77ce4bd3889820d67b52a5788357ac6f7b2f58 We need to automatically re…solve group membership into a boolean for theme object type settings which are of the group type, similar to what we did in the original commit above for group list type settings. This behaves in the same way -- for an object setting schema like this: ``` menu_sections: type: objects default: - name: section 1 groups: - 1 - 3 schema: name: menu section properties: name: type: string groups: type: groups resolve_group_membership: true ``` We replace `groups` with a boolean `user_in_groups` (groups is just the property name, it could be foo_bar etc.) and then you can do this on the client: ``` for (const section of settings.menu_sections) { if (section.user_in_groups) { // User is in at least one selected group for this section. } } ``` Rather than inspecting the `currentUser.groups`, which only includes visible groups, not all groups the user is a member of. This allows for more accurate permission checks for theme settings that are group based. Also c.f. https://meta.discourse.org/t/granular-group-based-permissions-for-anonymous-and-logged-in-users/402273/18?u=martin

另外 @Lilly，我从一个分支向你的 group-sidebar-menus 主题组件提交了一个 PR，以向后兼容的方式应用了此功能：

github.com/Lillinator/group-sidebar-menus

DEV: Apply resolve_group_membership changes from core (#5)

main ← martin-brennan:dev/apply-resolve-group-changes

opened 03:43AM - 16 Jul 26 UTC

martin-brennan

+23 -12

See https://github.com/discourse/discourse/pull/41756, which must be merged fir…st `resolve_group_membership` can now be used on group type of theme setting object settings, so instead of relying on currentUser.groups which only has visible groups in the client, we can use `user_in_groups` which is automatically resolved from the server side This is backwards-compatible with sites that don't yet have the core functionality deployed

接下来将处理 disallowed_groups 部分。

话题		回复	浏览量
Simpler and faster Category Settings page UX category-groups	23	424	2025 年3 月 27 日
Changes coming to settings for giving access to features (from trust levels to groups) Announcements trust-levels	30	5656	2025 年3 月 2 日
New category permission - "cannot see"/"exclude" Feature	36	4601	2024 年9 月 4 日
Add groups to the /about page Theme component about-page	22	699	2025 年3 月 21 日
Respect the visibility settings of all automatic groups Feature groups	14	883	2023 年10 月 23 日

为匿名和登录用户设置基于组的细粒度权限

相关话题