The dashboard shows a draft's public address, which only says the signup isn't ready
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 78/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- playwright, react, typescript
- Área
- accessibility, frontend, testing
Línea de trabajo
Empieza en src/app/app/(chrome)/page.tsx y comprueba cómo las filas del dashboard usan el estado de registro y muestran la dirección; lee DraftLine en src/components/signup/HeaderParts.tsx para ver el texto previsto. Actualiza la fila del borrador conservando las direcciones de los demás estados y, después, añade la comprobación de Playwright del dashboard descrita en el issue. Se considera terminado cuando el borrador muestra el mensaje y ninguna dirección, las demás filas conservan sus direcciones, las alturas de las filas coinciden en escritorio y a 390px, y pasan las comprobaciones indicadas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Needs your OK: this changes what a draft's row says on Your signups. Swap pipeline:proposed for pipeline:ready to have it built.
What happens
On Your signups (DashboardPage in src/app/app/(chrome)/page.tsx), every row shows the signup's address, /s/<slug>, in monospace under its title, whatever the signup's status. For a draft, that address isn't ready to send. Anyone who opens it gets "This signup isn't ready yet" until it's published. Next to the title, it reads like a working link.
The signup's own header is changing the same way. #499 asked that a draft show no public link, and #578 builds that for the header: in place of the link, a draft says "Only you can see this draft until you publish it." (DraftLine in src/components/signup/HeaderParts.tsx). #578 doesn't touch the dashboard, so this is the dashboard's half of the same idea.
To see it: create a signup and leave it as a draft. Go to Your signups. Its row shows /s/… under the title, like the published ones.
Fix, in outline
- For a draft, show "Only you can see this draft" in place of the address. Same muted, small line, in the body font rather than monospace, so every row keeps the same height.
- Keep the address for open, closed and archived signups. Their links lead to a real page: the signup, or a message saying it's closed or no longer available.
- No new query.
listSignupsForWorkspacealready returnsstatus.
Watch for
- The row's accessible name is everything in the link: title, address and status. For a draft it becomes the title, the new line and "draft". Check e2e specs that find a dashboard row by name.
tests/e2e/help/connect-an-ai-assistant.spec.tsmatches on the title only, so it's fine. - Same words as the header. If #578 has landed, take the words from
DraftLineso the two can't drift. If not, keep them in the dashboard and say so in the PR. - CHANGELOG: add a line under Unreleased › Changed.
Choices this makes
- A line in place of the address, not an empty space. Dropping the line would make draft rows shorter than the rest, and the "draft" pill alone doesn't say why there's no address.
- The words "Only you can see this draft". It's #578's line, cut short to fit beside the status pill at 390px. "Not published yet" is the other option.
- Drafts only. An archived signup's address also shows only a message, but #578 keeps the link in the header for closed and archived signups, and the dashboard should match.
Done when
- On Your signups, a draft's row shows "Only you can see this draft" and no
/s/…. Open, closed and archived rows show their address as now. - Rows are the same height whatever their status, on a computer and at 390px wide.
- A Playwright check on the dashboard with a draft and a published signup confirms which row shows an address.
pnpm lint && pnpm typecheck && pnpm knip && pnpm testpass.
Found by the UX walkthrough (scenario X1) 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
- 19 h 34 min
- PR fusionados (30 d)
- 165
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 signupAbiertoenhancement pipeline:proposed pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
richshaw/OpenSignup#653 ·
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 1 día. 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
-
A signup page's first Tab skips the header and lands on the next tabPosiblemente ocupada @richshaw la tomó hoy. Abiertobug good first issue pipeline:building pipeline:ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
richshaw/OpenSignup#644 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de richshaw/OpenSignup
Issues similares
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
ajv-validator/ajv#2689 ·
-
[Bug]: IME confirmation Enter can submit the SSH port-forward dialogPosiblemente ocupada @seijikohara la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
home-assistant/frontend#55323 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
lingdojo/kana-dojo#33188 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
self-driving
Dificultad 1/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día