loadsys / loadsys/composer-plugins

Move CakePHP-Skeleton `Console/` scripts here.

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
PHP
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
php
Domain
build-system, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.