Only the Date field's editor says that reminders are on, so an organizer who looks in Settings finds nothing about them
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 58/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- react, typescript
- Área
- frontend
Línea de trabajo
Start with src/app/app/(chrome)/signups/[id]/settings/page.tsx and read src/lib/reminder-fields.ts for sendsReminders and findReminderFields; compare the wording with InlineFieldForm.tsx and the help page’s Reminders section. Add read-only status for on, off, and no date field, using the reminder field’s label, and update the email line when reminders are on. Add tests for each state and the email wording, then run the listed lint, typecheck, knip, and test commands.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Needs your OK: this adds a short line about reminders to the Settings tab. Swap pipeline:proposed for pipeline:ready to have it built.
What happens
Reminders are on for every new signup with a Date field. People who gave an email get one the day before their slot. In the app, an organizer learns this in one place only: on the Build tab, under Fields, by editing the Date field. Its "Send a reminder email before this date" checkbox carries the explanation (InlineFieldForm.tsx). The other hints are small:
- The Fields list marks the reminder field with a bell. Its words, "Reminders sent the day before this date", are only a tooltip and a screen-reader label (
FieldsPopover.tsx). - The slot editor mentions reminders only once someone has signed up for that slot (
SlotEditor.tsx). - The help page "Create and publish your first signup" has a Reminders section.
The Settings tab says nothing about reminders while email is required. Its only line about emails is "We email everyone their link to change or cancel." (src/app/app/(chrome)/signups/[id]/settings/page.tsx). In the walkthrough, an organizer building a volunteer shift grid went to Settings and found no mention of reminders.
The switch is where it is on purpose. #200 put it on the date field and removed the Settings tab's Reminders card, so there is one place to change it (see the CHANGELOG, and the comment in the Settings page). That stays. What's missing is a line where organizers look, saying whether reminders are on and where to change them.
Fix, in outline
- A "Reminders" line on the Settings tab, in the "Sign-up form" card or a small card of its own. It's read-only, with no second switch. It says one of these, with the reminder field's own label in place of "Date":
- On: "People who give an email get a reminder the day before their slot's Date. To turn reminders off, open Fields on the Build tab and choose Date."
- Off: "Reminders are off. To turn them on, open Fields on the Build tab and choose Date."
- No date field: "No reminders: your slots have no Date field."
- Work it out on the server with
sendsReminders(sig.settings)andfindReminderFields(src/lib/reminder-fields.ts), from the signup the page already loads. The tab stays a plain server-rendered page with no script of its own. - The email line says it too. With reminders on, "We email everyone their link to change or cancel." becomes "We email everyone their link to change or cancel, and a reminder the day before their slot."
Watch for
- One switch. Don't add a toggle here unless the owner picks that option below.
- The same words as the builder. Match the field editor's "Sent the day before" and the help page's
REMINDER_WHEN, which readsREMINDER_LEAD_HOURS. - Email optional. The Optional line already says people without an email get no reminders. Keep it.
- Help. Add a sentence to the Reminders section of the help page saying the Settings tab shows whether they're on. Open PRs #574, #576, #578, #580 and #581 also change that page. Whichever lands second has a small merge.
- The CHANGELOG. The legal pages need no change: nothing new is stored or sent.
Choices this makes
- On the Settings tab, read-only. It's where the walkthrough's organizer looked, and it keeps #200's one switch on the date field. The alternatives:
- An on/off switch on Settings for
sendReminders, with the date field still choosing which date. More direct, but it brings back the card #200 removed. - A line on the Build tab, for example beside the Fields button. Closer to the switch, but the Build tab is already busy.
- An on/off switch on Settings for
- The wording above, in plain words as
docs/writing-help.mdasks. - No link that opens the Fields dialog. The text names the steps instead. A link that opens the dialog on the Date field would need a way into the Build tab's state, like #580's
BuildBridge.
Done when
- The Settings tab shows the right line when reminders are on, when they're off, and when the signup has no date field, with the field's own label. A test pins each.
- With reminders on and email required, the email line mentions the reminder.
pnpm lint && pnpm typecheck && pnpm knip && pnpm testpass.
Found by the UX walkthrough (scenario O2) on 2026-10-24, and checked against the code on main at 4ed27a9.
Generated by Claude Code
- Lenguaje dominante
- TypeScript
- Estrellas
- 19
- Forks
- 4
- Merge medio
- 21 h 3 min
- PR fusionados (30 d)
- 176
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de richshaw/OpenSignup
-
enhancement pipeline:proposed pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
richshaw/OpenSignup#654 ·
Los mantenedores suelen responder en 1 día
-
The help pages never say "pause", so organizers looking for it miss Close or reopen a signupPosiblemente ocupada @richshaw la tomó hoy. Abiertoenhancement pipeline:building pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
richshaw/OpenSignup#653 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
enhancement pipeline:proposed pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
richshaw/OpenSignup#652 ·
Los mantenedores suelen responder en 1 día
-
SMTP timeout notes in smtp.ts and the changelog describe nodemailer 10.0, not 10.1Posiblemente ocupada @agammann la tomó hace 2 días. Abiertoenhancement good first issue pipeline:ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
richshaw/OpenSignup#645 ·
Los mantenedores suelen responder en 1 día
-
enhancement pipeline:proposed pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
richshaw/OpenSignup#589 ·
Los mantenedores suelen responder en 1 día
Todos los issues de richshaw/OpenSignup
Issues similares
-
New icon: `filter-clear`Abiertocalcite-ui-icons enhancement impact - p3 - not time sensitive needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Esri/calcite-design-system#15467 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
diegosouzapw/OmniRoute#18390 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 86/100
guilhermerodz/input-otp#157 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
davidjerleke/embla-carousel#1414 ·
Los mantenedores suelen responder en 4 días