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

Ship the bundle's own Doctrine migrations, so apps don't generate them

Cerrado
  • ¿Algo no está bien?
#556 1 comentario 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
php, symfony
Área
backend, database

Línea de trabajo

Start by reading the bundle's Doctrine entity mappings and the existing migration configuration to identify the tables and migration entry points involved. The proposal leaves baseline strategy, adoption by existing apps, supported database platforms, and ordering unresolved, so those decisions need to be settled before implementation. Done means the bundle ships migrations for its mapped schema and apps can adopt them without regenerating those migrations locally.

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

Descripción

Proposal

The bundle ships Doctrine migrations for its own schema: every table its entities map. Apps then receive them with composer update, through doctrine_migrations.migrations_paths with a bundle namespace.

Why

Almost every table in a CWA app belongs to the bundle's entities. Today each app generates migrations for them itself (doctrine:migrations:diff after updating the bundle), and the template's downstream sites copy the template's generated files. That causes three problems:

  • Data migrations aren't shared: diff only produces schema changes, so a backfill the bundle needs has to be copied by hand.
  • Sites drift: each app's generated SQL can differ slightly from the next.
  • Every bundle schema change needs a template release and a copy step in every downstream site.

If the bundle shipped them, the template would only need migrations for its own entities (today just the Redis watch state). It would also make squashing the template's history at beta simpler: https://github.com/components-web-app/components-web-app/issues/192

Questions for the bundle

  • One baseline at the bundle's beta, then incremental migrations?
  • How existing apps take over: their databases already have these tables from their own generated migrations. They'd mark the bundle's baseline as done (doctrine:migrations:version --add) once, after checking diff is clean.
  • Database platforms: PostgreSQL first? The bundle already lists PostgreSQL, MySQL, MariaDB and SQLite for route-security rules.
  • Ordering between bundle migrations and an app's own (Doctrine sorts by version across namespaces).
Lenguaje dominante
PHP
Estrellas
32
Forks
8
Merge medio
56 min
PR fusionados (30 d)
164

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 components-web-app/api-components-bundle

Todos los issues de components-web-app/api-components-bundle

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.