Детальные групповые права доступа для анонимных и авторизованных пользователей

martin · 16.Июль.2026 03:48:29

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 я создал PR для вашего компонента темы group-sidebar-menus из форка, который применяет эту функциональность с обратной совместимостью:

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	27.03.2025
Changes coming to settings for giving access to features (from trust levels to groups) Announcements trust-levels	30	5656	02.03.2025
New category permission - "cannot see"/"exclude" Feature	36	4601	04.09.2024
Add groups to the /about page Theme component about-page	22	699	21.03.2025
Respect the visibility settings of all automatic groups Feature groups	14	883	23.10.2023

Детальные групповые права доступа для анонимных и авторизованных пользователей

Связанные темы