Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

auth plugin: let child apps add a section to Settings → Profile

Abierto
  • ¿Algo no está bien?
#661 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience

Línea de trabajo

Start by reading the auth plugin's implementation of Settings → Profile and the runtime configuration in bos.app.ts; the issue does not name their file paths. Define a supported way for child apps to declare ordered sections and for the plugin to render them with signed-in user context and recover from load failures. Done means child apps can add sections without claiming /settings/profile or forking the page; the separate redeem hook is identified as a possible follow-up.

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

Descripción

Problem

Settings → Profile (/settings/profile) comes from the published auth plugin, so a child app has no way to add its own section there. City Node needs one for a member's attendance record across communities (NEARBuilders/citynode.app#400). For now that list lives on City Node's Home page, while the issue asks for it on Profile.

Proposal

A small, declared extension point on the Profile page, for example:

  • the child app lists profile sections in its app config (bos.app.ts), each with a title and a remote component (or a route path) from the child's UI remote
  • the auth plugin renders them below its own Profile fields, inside its layout, in the configured order
  • if a section fails to load, it shows an error and retry, and the rest of the page keeps working
  • the sections get the signed-in user's context; they read their own data through the child's API

Whatever shape fits the runtime is fine. The main ask is a supported way to do this, so child apps don't have to claim /settings/profile locally and fork the page.

Related, smaller

City Node only learns about a check-in when an organizer opens the community Overview and it syncs from listOnboardingCodes / getOnboardingStatus. A redeem hook or event (child app notified after a successful onboarding-code redeem, with org, code, user and event id) would let the record update right away, without touching the QR → passkey → joined flow. Happy to split this into its own issue.

Context

  • City Node side: getMyAttendance / reconcileAttendance in api/, and the AttendanceRecord component, both merged in NEARBuilders/citynode.app#463
  • Epic: NEARBuilders/citynode.app#408
Lenguaje dominante
TypeScript
Estrellas
5
Forks
3
Merge medio
9 h 37 min
PR fusionados (30 d)
157

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 NEARBuilders/everything-dev

Todos los issues de NEARBuilders/everything-dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.