Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Admin: policy-based authorization + member management endpoints (Phase 8.1, 8.2, 2.6)

Aperta
  • Qualcosa non va?
#1 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
csharp, postgres
Ambito
api, authorization, backend, databases, search, testing

Direzione di ricerca

Inizia leggendo la convenzione esistente IEndpointModule.MapEndpoints e l’harness in tests/CommunityPro.Tests/Members/MembersTestHarness.cs. Traccia i contratti pubblici e i percorsi degli eventi per Identity/Members, i refresh token, i profili e la ricerca prima di implementare il gruppo di amministrazione e gli endpoint. Il lavoro è completo quando ogni criterio di accettazione viene superato con la copertura xUnit, inclusi la policy, il comportamento degli endpoint, il filtraggio della disattivazione e la rimozione dell’indice.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

admin

Scope

Foundation for everything /admin/*: an admin authorization policy, plus the member-management endpoints. Also closes deferred item 2.6 (hide deactivated members) since deactivation is introduced here.

The admin role already exists in Identity (Phase 1). This ticket adds:

  1. An AdminPolicy (role admin, checked server-side on every request — DB-backed like ActiveMemberPolicy, not stale claims) and a reusable route-group pattern so other modules can mount /admin/* endpoints with the policy applied at group level.
  2. Member management endpoints (Identity/Members owned, /admin/* paths):
Method Path Notes
GET /admin/members paginated; filter by status; search by login/display name
POST /admin/members/{id}/activate manual activation — fallback for the orphan-PR edge case; runs the same pipeline as the webhook (publishes MemberActivated)
POST /admin/members/{id}/feature toggle MemberProfile.IsFeatured (drives spotlight)
POST /admin/members/{id}/deactivate sets Deactivated, revokes refresh-token families, publishes MemberDeactivated
  1. Deferred item 2.6: Members module subscribes to MemberDeactivated → profile is removed from the Meilisearch index and excluded from /members, /members/{id}, and /members/spotlight at query level (not UI level).

Error codes

admin.forbidden, members.not_found, members.already_active, members.already_deactivated

Acceptance criteria

  • Admin policy rejects non-admin active members (403) and is applied at the route-group level
  • Manual activation is idempotent and fires the same events as webhook activation
  • Deactivation revokes all refresh tokens for the user
  • Deactivated members disappear from list/detail/spotlight endpoints and from the search index (test each)
  • xUnit coverage for policy, each endpoint, and the MemberDeactivated handler
Conventions (project-wide, non-negotiable)
  • .NET 9, records for immutable shapes, file-scoped namespaces, primary constructors where they read well. Minimal-API endpoints grouped per module via IEndpointModule.MapEndpoints.
  • Result<T> (SharedKernel) instead of exception-driven control flow. Endpoint results map failures to ProblemDetails with the stable error codes listed above — the frontend keys off them.
  • Module owns its EF Core DbContext mapped to its own Postgres schema. Modules never reference each other's internals — cross-module needs go through a public contract interface or an in-process domain event (IEventPublisher).
  • All external calls (GitHub, Stripe, Brevo, Cloudinary, Meilisearch) behind interfaces owned by the consuming module.
  • Every list endpoint paginated (offset is fine). xUnit tests in tests/CommunityPro.Tests/<Module>/ following the existing harness patterns (see Members/MembersTestHarness.cs).
Lingua principale
C#
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CommunityPro/community-pro-api

Tutte le issue di CommunityPro/community-pro-api

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.