Release gate: run init and generate auth on the Tailwind consumer

Abierto
  • ¿Algo no está bien?
#179 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@fetrarij ya está trabajando en esto.

Desde el 12/11/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
78/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
angular, tailwindcss, typescript
Área
ci-cd, testing

Línea de trabajo

Read CONTRIBUTING.md, then trace the Tailwind consumer setup in tools/release-gate/consumer.mjs, including CONSUMERS.tailwind, generatedFiles() and initWithBin(). Follow the Tailwind consumer calls in tools/release-gate/run.mjs and the generated page check in tools/release-gate/e2e/consumer-tailwind.spec.ts. Done means both CLI flows build successfully, the E2E opens the generated sign-in page, the full gate catches the #177 regression, and release gate docs list both steps.

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

Descripción

enhancement layer: tooling pkg: cli

What is wrong

The release gate never runs the CLI on a Tailwind app, so a generated Tailwind file that does not compile reaches a release unnoticed. #177 is an example: the Tailwind sign-in page written by pidrang init and pidrang generate auth did not compile, and the gate passed.

In tools/release-gate/consumer.mjs:

  • the tailwind consumer installs @pidrang/core, @pidrang/supabase and @pidrang/tailwind only (line 55), so it has no pidrang bin and --generator bin cannot run on it;
  • generatedFiles() writes a layout only for material (line 195), and initWithBin() always generates Material files (line 262).

What we want

  • The tailwind consumer also installs @pidrang/cli and @pidrang/cli-supabase.
  • The gate runs pidrang init on the tailwind consumer with the sign-in page, as it does for material, then ng build.
  • The gate runs pidrang generate auth on a Tailwind app, then ng build.
  • tools/release-gate/e2e/consumer-tailwind.spec.ts opens the generated sign-in page.

Done when

  • With the bug of #177 put back, node tools/release-gate/run.mjs --mode full fails on the tailwind consumer.
  • Without it, the full gate passes.
  • docs/ that describe the release gate list the Tailwind init and generate auth steps.

Where to look

  • tools/release-gate/consumer.mjs: CONSUMERS.tailwind, generatedFiles(), initWithBin().
  • tools/release-gate/run.mjs: the consumer('tailwind', ...) calls.
  • tools/release-gate/e2e/consumer-tailwind.spec.ts.

Read CONTRIBUTING.md before opening the pull request.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
2
Merge medio
9 h 17 min
PR fusionados (30 d)
48

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 pidrang/pidrang

Todos los issues de pidrang/pidrang

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.