Load the helper files through Composer autoload instead of a boot stage
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
- 52/100
Línea de trabajo
Start with composer.json (add the 30 helper paths under autoload.files) and LoadHelpersStage, which currently globs src/*/Helpers and runs require_once on each file; keep only the application and module helper loading there. Add a test that compares the files in src/*/Helpers with the autoload.files list in both directions, then run composer dump-autoload and the test suite. Done when every helper is callable after vendor/autoload.php, the boot no longer scans src/*/Helpers, and the CI checks pass.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Declare the framework's 30 helper files in autoload.files of composer.json, and stop scanning for them in LoadHelpersStage.
Why
LoadHelpersStagefinds the component helpers on every boot: it scanssrc/*/Helperswithgloband runsrequire_onceon each file. The rootcomposer.jsonhas nofilesentry today.- The helper files are plain function definitions. They have no constants and no code that runs when the file is included, and only two files have guards (the
cron_*functions and thegetallheaderspolyfill), which is the shape Composerfilesexpects. - A static list from Composer replaces about 26 directory scans on every boot, and tools such as PHPStan and IDEs see the functions without booting the application.
- The packages are to be extracted into separate Composer packages from 4.0, each with its own
composer.jsonand its own helpers. If the helpers are already declared withautoload.filesin the monorepo, extraction only moves each package's list into its owncomposer.json.
Scope
- Add the 30 helper files (26 packages:
Apphas 4,Environmenthas 2, every other package has 1) toautoload.filesincomposer.json. - Remove the component part of
LoadHelpersStage. It keeps loading the application'shelpers/and each module'shelpers/, which are the application's own files. - Add a test that fails when a file in
src/*/Helpersis not listed inautoload.files, or when a listed file does not exist. Without it, a new helper file that is not added tocomposer.jsonshows up only as "undefined function". - Update the documentation that describes helper loading at boot (the App architecture page) when this is released.
Notes
- The helpers become available as soon as
vendor/autoload.phpis included, not at boot. They useDSonly inside function bodies, so loading earlier is safe. - Adding a helper file needs an entry in
composer.jsonand acomposer dump-autoload, instead of being picked up by the scan. - When a package is later extracted, the paths in its list may change if its folder layout differs from
src/<Package>/Helpers/.
Out of scope
- Extracting any package.
- Loading the application's and the modules' helpers.
- Changing what any helper function does.
Acceptance criteria
- every helper function is available right after
vendor/autoload.php, without booting the application - the boot no longer scans
src/*/Helpers - the application's and the modules' helpers still load, in the same order after the framework's
- the new test fails for an unlisted helper file
composer test,composer cs:check,composer phpstanandcomposer rector:checkpass on every PHP version in the CI matrix
- Lenguaje dominante
- PHP
- Estrellas
- 43
- Forks
- 22
- Merge medio
- 54 min
- PR fusionados (30 d)
- 57
Preparar el entorno
- Sin Dockerfile ni 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 quantum-php/framework
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
quantum-php/framework#692 ·
Los mantenedores suelen responder en 1 día
-
routing testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
quantum-php/framework#547 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
quantum-php/framework#694 ·
Los mantenedores suelen responder en 1 día
-
Raise PHPStan to level 9Abiertorefactoring tech debt
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
quantum-php/framework#693 ·
Los mantenedores suelen responder en 1 día
-
install:debugbar reads the package folder from the working directory and uses the default storage adapterPosiblemente ocupada @armanist la tomó hoy. Abiertobug console debugbar good first issue
quantum-php/framework#691 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de quantum-php/framework
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
ajeetraina/awesome-docker-sbx#559 ·
-
dependencies enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
novalo-dev/Prestashop-MCP-Server#329 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
bug origin:interactive status:available
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Ultimate-Multisite/ultimate-multisite#2131 ·
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día