Constraints of a grant in the role editor: sites, locales, fields, resources and a row rule (A-52)

Abierto
#3,430 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Read sections 4.15 and 10.7 of docs/planning/admin-technical-spec.md, then review the role editor work in A-32 and the row-rule registration issue #3417. Implement the grant constraints in the role editor and cover each constraint and request with component tests; add the locale-limited role end-to-end case. Done means the acceptance cases pass, including preserving resources and rejecting an unregistered rule on its field.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:admin type:feature

Problem

Rows 4.4 to 4.7 narrow a grant to sites, locales, fields and the rows a registered rule selects, and a grant may also be limited to resources, such as the media folders of decision record 0004. A-32 edits a role and its grants and keeps these constraints as it read them. Nothing in the admin sets or changes one.

Proposal

The constraints of a grant in the role editor of A-32 (4.15):

  • Sites, from the sites the caller may manage, and locales, from the locales of those sites.
  • Fields, for a permission of a content type, from the fields of that type in GET /schema.
  • A registered row rule, picked from the rules registered for the grant's content type (#3417). Until that route is merged, a stored rule is kept and shown by its name, and a new one is typed by name, with FCMS3042 shown on the field.
  • resources, which the specification of the editor leaves out and the API has: shown as stored and kept on a save. Where the admin can name them it does, and the media folders of a media grant are the first such case; any other kind stays a list of the ids as stored.
  • A constraint that does not narrow the grant is left out of the request, as the server stores it.

Acceptance

  • An administrator limits a grant of a content type to one site, two locales and three fields, saves, and reads the same back
  • A row rule is set on a grant and refused by name when it is not registered, with the refusal on its field
  • A grant limited to resources keeps them through an edit of its other constraints
  • A user of a role limited to one locale may change an entry in that locale only, checked through the admin
  • Component tests cover each constraint and the request they make; an end-to-end case limits a role to a locale and signs in as its user

Design: docs/planning/admin-technical-spec.md, sections 4.15 and 10.7 (A-52). Rows 4.4 to 4.7. Needs A-32, and #3417 for the list of row rules. Split from A-32 when A6 was planned. Size: M.

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.