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

New signups don't start in their organizer's language

Abierto
  • ¿Algo no está bien?
#627 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
next.js, typescript
Área
backend-api-design, internationalization

Línea de trabajo

Start with the listed signup routes, the New signup form action, MCP create_signup input, and src/lib/magic-compose/persist.ts; read the organizer locale work in #626 first. Trace each create path and its telemetry, then update the tool docs, registry snapshots, privacy page, telemetry docs, and CHANGELOG. Done means tests cover each create path and localeSource, MCP locale handling, and the listed lint, typecheck, knip, test, and database checks pass.

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

Descripción

enhancement pipeline:proposed pipeline:ux

Needs your OK: this makes every new signup take its organizer's language, whether it's made in the browser, by Magic Compose, through the API or by an AI assistant. Nothing changes until Swedish ships. create_signup gains an optional locale. Swap pipeline:proposed for pipeline:ready to have it built.

What happens

Signups have a language (#625) and organizers have one (#626), but nothing connects them: a new signup gets no language.

Fix, in outline

  • The rule. A new signup's language is the one an API or MCP caller sent; otherwise, the organizer's effective language (getOrganizerLocale, #626). The route decides and passes it into the service, so services stay pure.
  • Only once there's a choice. While SHIPPED.participant holds only English, creates store nothing, unless a caller sends a shipped value. That way no signup is pinned to an English nobody chose; these signups follow resolveLocale when read.
  • Every create path:
    • the browser route (src/app/api/signups/route.ts) and the New signup form's action;
    • Magic Compose (src/app/api/signups/magic-compose/route.ts);
    • MCP.
  • MCP create_signup.
    • Add an optional locale to its input with .extend(). Don't put it on FullDraftSchema, which is also Magic Compose's output schema.
    • Strip it before persistDraft, which takes the language as an option and puts it in createSignup's settings (src/lib/magic-compose/persist.ts).
    • Without one, the signup takes ctx.locale from #626.
    • An unsupported value is invalid_input, with a suggestion listing the allowed values.
    • Magic Compose passes the organizer's language through the same option.
  • Telemetry. signup.created gains locale and localeSource (setting | instance | browser | api | default); document both in docs/telemetry.md. The privacy page's activity-log sentence gains them, because browser records a fact taken from the organizer's browser. Its "Last updated" date moves.
  • Docs: the tool description, the registry snapshots, and docs/connect-ai-assistant.md. src/mcp/instructions.ts needn't change, because without a locale the organizer's own language applies.

Watch for

  • Changing the organizer's language later doesn't move existing signups. The language is stored on each signup.
  • Keep groupByFieldRefs as persistDraft builds it today.
  • Add a CHANGELOG entry.

Choices this makes

  • No language picker on the New signup page. Default: none. Most signups are in their organizer's language, and the rest are changed in the signup's Settings tab.

Order

After #626, because the organizer's language and ToolContext.locale come from it.

Done when

  • Tests cover each create path and each localeSource, plus create_signup with a locale, without one, and with an unsupported one.
  • The MCP registry snapshots are updated.
  • pnpm lint && pnpm typecheck && pnpm knip && pnpm test and pnpm test:db pass.

Planned with the owner in https://claude.ai/code/session_01EFKmj716ZY3b3SwR8TV8Y2 and checked against the code on main at 35288fa. The full plan is private to the owner's account: https://claude.ai/artifact/VgQH6U2s2EVx3LX991fJi8 (a Claude session on that account can open it with the Artifact tool's read action). This is part of step 1.1 there.

Lenguaje dominante
TypeScript
Estrellas
19
Forks
4
Merge medio
19 h 34 min
PR fusionados (30 d)
165

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 richshaw/OpenSignup

Todos los issues de richshaw/OpenSignup

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.