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

オープン
#3,428 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
csharp

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C#
スター
567
フォーク
107
平均マージ
1時間 19分
マージ済み PR(30日)
353

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fluentcms/FluentCMS のほかの issue

fluentcms/FluentCMS の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。