Members and member groups pages of the admin (A-40)

Ouverte
#3,428 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
csharp

Piste de recherche

Read sections 4.15 and 10.7 of docs/planning/admin-technical-spec.md, including AQ11 and the dependency on A-51. Then inspect the administration assembly, the Management API routes for /members and /member-groups, and their OpenAPI definitions. Done means the member and group pages meet the listed permission, keyboard, component, API, and end-to-end acceptance criteria.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:admin type:feature

Problem

Row 4.10 (Must) gives a site members and member groups, which row rules and public access read (rows 4.6, 4.8), and it has no other user interface than the pages of row 4.22, a Should taken early (AQ11). The Management API has /members and /member-groups, and the admin has no page for them.

Proposal

Pages in the administration assembly (4.15), for a caller who holds members.manage for the instance:

  • /members: the list, read in pages, with search and the filters group, verified and active.
  • /members/{id}: the member with its sessions, each with revoke, its external logins, each with remove, and its groups; create, change, deactivate and reactivate, and delete after a confirmation that names the member.
  • /members/groups: the groups with their role; create, change (the name and the role) and delete; a member added to and taken out of a group.
  • Binding a group to a role, and putting a member into a group, need the grants of the group's role: the refusal is shown by what it means (FCMS3103).
  • The custom profile fields of row 4.22 stay out (AQ11).

Acceptance

  • An administrator finds a member by search and by group, ends one of its sessions, deactivates it and deletes it
  • A group is made, bound to a role, given a member and loses it again
  • A caller below the group's role sees the refusal named
  • A caller who holds members.manage through a site role only sees no entry and no page
  • The pages are usable by keyboard alone
  • Component tests cover the list, the detail and the groups; the API tests check the records against the OpenAPI document; an end-to-end case makes a group and puts a member into it

Design: docs/planning/admin-technical-spec.md, sections 4.15 and 10.7 (A-40), AQ11. Rows 4.10, 4.22. Needs A-51. Size: M.

Langage dominant
C#
Étoiles
567
Forks
107
Merge moyen
1 h 19 min
PR mergées (30 j)
353

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fluentcms/FluentCMS

Toutes les issues de fluentcms/FluentCMS

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.