Move CakePHP-Skeleton `Console/` scripts here.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- php
- Domain
- build-system, tooling
Research direction
Start by inspecting the CakePHP-Skeleton's Console/ scripts, composer.json, composer.json.template, and the existing *.template replacement tests. Move the composer-only scripts and related tests into this package, then verify that generated projects no longer retain the directives or script copies while the post-create-project-cmd behavior still works.
Written by the indexing model from the issue text.
Description
Currently our CakePHP project skeleton bundles some composer post-create-project-cmd scripts directly in its own repo. This is inconvenient, because these files end up being copied unnecessarily into every Cake 3 project we spawn from the skeleton.
A good solution is to move those composer-only scripts into their own repo, which can be included via composer. This way the CakePHP-Skeleton's composer.json can require loadsys/composer-plugins, (and include the post-create-project-cmd entry) but the generated projects (which use composer.json.template) do not have to retain a copy of either directive.
This will also help clean up the unit tests for the *.template replacement by moving them into this repo. This will close loadsys/CakePHP-Skeleton#72 and better fix loadsys/CakePHP-Skeleton#126
- Dominant language
- PHP
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from loadsys/composer-plugins
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Write missing tests.Openenhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in loadsys/composer-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
filamentphp/filament#20630 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenAPITools/openapi-generator#25107 ·
Maintainers usually reply within 1 day
-
needs-maintainer-review review:approve
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Ultimate-Multisite/ultimate-ai-connector-compatible-endpoints#163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day