Proxying git command arguments as is i.e. ./yii-dev git/commit --message="xxxx" --amend etc. would make working with git batch commands more convenient.

Alternative idea is to have a command that just does a batch execution of any commands in each repository.

Sorry if this is an inappropriate question for current package, but where contained MVC reflection/helpers? What classes/methods have that's functionality?

How get list of

• module/application controllers/commands
• controller actions
• route controllers and actions (controllers/actions matches route)

How check/validate

• class is controller/command
• method/class is action

How convert

• class name to controller/command id
• method/class name to action id

A command that resolves package dependencies and checks if there are circles. If there are, highlights problematic packages.

It should take into account require-dev of the current package as well.

Would be nice to have command that will fork origin repository and mark in packages.php to use forked repository.

Related to #95

"config": {
    "sort-packages": true
},

Would make composer sort require and require-dev alphabetically. Would result in less configs and more readable dependencies list.

I think "test" command may be very handy.
For example, I've modified one related package and want to test another packages.

Problem

Modified package can't be tested as an integration of some packages.

User story

As a developer I want to call in console ./yii-dev test [packages delimited with comma] and all selected packages should be tested.

Possible solution

Implement composer test command in any yiisoft/* packages.
./yii-dev test [packages delimited with comma] will check if command is available then it will be called.

Workflow could be similar to ./build/build release from Yii 2.

https://github.com/yiisoft/yii-dev-tool/blob/master/replicate.php#L5 there could be another section in the config called "filesToDelete".

Instead of using a composer binary that is assumed to be in the path I propose downloading our own binary and running it with a different configuration directory.

This will allow us, for example, to enable: https://github.com/hirak/prestissimo for faster installation.

We have migrated from phan to psalm partially.
I think we need to remove any phan mentions from packages.

For example:

$ ./yii-dev status
▶ Git status of package docs

 M guide/en/README.md

▶ Git status of package di

✔ nothing to commit, working tree clean

▶ Git status of package injector

✔ nothing to commit, working tree clean

Since we are aware that we executed status command there is no need to remind it:

$ ./yii-dev status
▶ docs

 M guide/en/README.md

▶ di

✔ nothing to commit, working tree clean

▶ injector

✔ nothing to commit, working tree clean

I suggest to add .gitignore to replicated files and replicate it.
https://github.com/yiisoft/yii-dev-tool/blob/master/config/replicate/files.php#L1

This issue blocked by #107

Composer errors are hard to spot, the install command should:

• Catch exit codes
• Summarize errors at the end of execution

At the very least it should provide a note like "some packages have dependency issues".

Would be nice to have an ability to use upstream/master when you using a fork.
master from fork can be outdated and you will work with outdated code base.

I think it can be configured in packages.php like the following:

return [
    // ....
    'yii-web' => [
        'upstream' => 'yiisoft/yii-web',
        'origin' => 'xepozz/yii-web',
    ],
    // ....
];

or any handy ways.

OS: Windows 10
packages.local.php:

$packages = [
    'auth' => 'https',
    'yii-console' => 'https://github.com/roxblnfk/yii-console.git',
    'yii-cycle' => 'https://github.com/roxblnfk/yii-cycle.git',
    'yii-web' => 'https://github.com/roxblnfk/yii-web.git',
    'yii-demo' => 'https://github.com/roxblnfk/yii-demo.git',
];

Can't execute yii-dev update for any forked package

yii-dev update auth works good

yii-dev update yii-console works not good :

upstream and origin configured automatically:

See #136 (comment)

This change will make able to update all packages with one call yii-dev update. Now I need to run two commands one after another: yii-dev git/pull and yii-dev update.
If anyone want to have composer/update command we can make separated command.

We do not have detailed explanations on how to use yii-dev-tool. Especially not enough examples of use. This can reduce the involvement of people in the development.

I propose to add:

• Workflow examples in yii-dev-tool README
• Cross references in yiisoft/docs
• Forum post

Related docs:

• yiisoft/yii-dev-tool – README
• yiisoft/docs – Yii Development Tool

Related forum posts:

• Yii development tool
• Contributing to Yii 3

See example https://www.techempower.com/benchmarks/#hw=ph&l=zik073-f

Now this tool is used only for Yii 3, but it would be convenient to use it for developing other projects, for example, a project based on modules.

What needs to be changed/added:

• Extract core files to yiisoft/dev-tool and add dependency it to yii-dev-tool

• Make configuration of repositories possible, decouple from yii

• Add a command that creates a package from a template

• Add a command to run unit tests in packages

Ability to echo less messages is helpful for group commands such as ./yii-dev status. Instead of outputting

▶ Git status of package yii-base-web

✔ nothing to commit, working tree clean

▶ Git status of package yii-project-template

✔ nothing to commit, working tree clean

▶ Git status of package yii-demo

 M src/Controller/SiteController.php

when the option is on we can display only items requiring attention:

▶ Git status of package yii-demo

 M src/Controller/SiteController.php

All this time I have been using my Vargant configuration for yii-dev-tool.

This is a ready-to-use Vagrant playground that can be used to develop Yii3 packages. This is an alternative to Docker. It contains:

• Ubuntu 18.04
• PHP 7.2
• Composer with prestissimo plugin
• xDebug
• unzip, htop, mc (Midnight Commander)
• some other handy presets

In the future, we can add web configurations for packages like yii-demo to this Vagrant configuration.

I suggest adding it directly to yii-dev-tool repository so that it is available to run right from the yii-dev-tool package.

I have this problem with docker-compose when I run docker-compose run --rm php bash:

ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

The solution for this was change the version in docker-compose like this:

version: '3.4'
services:
  php:
    image: yiisoftware/yii-php:7.4-apache
    working_dir: /repo
    volumes:
      - .:/repo
      # For composer usage in container; NOTE! There may be performance issues, see also https://github.com/docker/for-mac/issues/77
      - ~/.composer-docker/cache:/root/.composer/cache:delegated

Change version 2.4 to 3.4.

Mi version of docker-compose is:

docker-compose version 1.17.1

Can I send a PR to update?

Thanks!

Now the tool is usable for work, because many packages are in dev status.

But let's imagine the following situation after the packages are released:

1. Package A requires version ^2.0 of package X.
2. Package B requires version ^1.7 of package X.
3. Package C requires dev-master of package X.

But the tool only installs one version of the X package and creates symlinks for one version. Manual version control with so many repositories can be very tedious...

I currently have no solutions for this problem. But we need to think about this beforehand.

Current state

Now the commands look like this:

Proposal

1. Group ungrouped commands.
2. Create aliases for frequently used commands.

Plan

1. Group commands (rename):

• exec -> shell/exec
• install -> package/install
• update -> package/update
• lint -> package/lint
• test -> package/test

2. Create aliases:

For example, I have part of all packages (only 10). I want to update all these packages and I don't want to install other packages.
When I do ./yii-dev update it starts installing all missed packages.
I think we shouldn't install missed packages in update mode

Like link in symfony: https://symfony.com/doc/current/contributing/code/pull_requests.html#use-your-branch-in-an-existing-project

Could be a handy tool that checks dependencies are correct:

1. Get package composer.json. Read require and require-dev packages.
2. For each package get its root namespace from its composer.json, search for its usage within src and tests.
3. If used in src or config/common.php / config/web.php - should be in require.
4. If used in tests / config/tests.php only - should be in require-dev.
5. If not used - should be removed.

When I was working on PR #21 I realized that logic of declaring packages in the package configuration is strange...

Suppose the main package configuration looks like this:

<?php
$packages = [
    'yiisoft/di' => 'di',
    'yiisoft/injector' => 'injector',
    'yiisoft/factory' => 'factory',
    'yiisoft/access' => 'access',
];
if (file_exists($localFile = __DIR__ . '/packages.local.php')) {
    $packages = array_merge($packages, require $localFile);
}
return $packages;

Suppose my own packages.local.php looks like this:

<?php

$packages = [
    'rugabarbo/di' => 'di',
    'rugabarbo/docs' => 'docs',
    'rugabarbo/factory' => 'factory',
    'rugabarbo/yii-captcha' => 'yii-captcha',
];

return $packages;

The array keys are the names of GitHub repositories, and the values are the names of /yii-dev-tool/dev/ subdirectories. It would be logical for my package factory to replace yii package factory after merge, but after merge we get the following array:

[
    'yiisoft/di' => 'di',
    'yiisoft/injector' => 'injector',
    'yiisoft/factory' => 'factory',
    'yiisoft/access' => 'access',
    'rugabarbo/di' => 'di',
    'rugabarbo/docs' => 'docs',
    'rugabarbo/factory' => 'factory',
    'rugabarbo/yii-captcha' => 'yii-captcha',
];

Here we see that folders di and factory are each connected to two different repositories, but the logic of the tool is such that the code from only one repository will actually be installed in the folder. And the most interesting: which one will be installed depends on the sequence of user actions :)

So something is wrong here. Function array_merge() doesn't seem to be suitable for merging these configurations or the configuration structure itself should be different.

If you use --httpd the result is that the help text is displayed. The problem is that adding the option moves where the command is located in $argv.

To get it working, I separated the command line processing into a new class: src/command/Args.php and using getopt() to parse with both long and short arguments specified.

Added --verbose for future use.

Will wait on pull request until I get a go signal. You can preview at BillHeaton/yii-dev-tool. Look for yii-dev-tool-fix-28.

When you want to reset all packages to master branch you get an errors

Package requirements repository is not cloned.
To fix, run the command:

  ./yii-dev install requirements

You can also disable the package in packages.local.php
See packages.local.php.example for configuration examples.

and the same for other not installed packages.

I expect when I do git/checkout master that will be checkout only installed packages.

Apparently there is no easy way to set up the initial forks on the packages listed packages.php

./yii-dev setup

would be most helpful. Any suggestions for interim would be gratefully accepted.

As briefly discussed on slack, it's becoming harder and harder to understand build failures in Yii 3 repos, as packages are inter-dependent and a tiny change in A can brake B without us noticing for days.

As a counter measure, could we setup Travis cronjobs as suggested by @rob006 on all repositories to run like every 2 days? (still unsure about the right periodicity)

See https://git-scm.com/docs/git-request-pull
https://cli.github.com/manual/gh_pr_create

I tried to setup new package to app-api and I had a problem:
Composer don't read actual file composer.json from vendor folder, it cached them in vendor/composer/installed.json instead.
Because of this behaviour new package won't be added to config folder.

Composer version 2.0.8 2020-12-03 17:20:38
yii-dev-tool: 466ca89ee96dfe24e037f4d0a870d00e3d8eaf28 (commit hash)

Would be nice to make builds for phpbenchmarks.com after that it will support PHP 7.4

• Framework
  • Hello world
  • REST API
• Template ( ? )
• Json Serializer ( ? )

When used with yii-console that registers its binary via the following

"bin": [
    "bin/yii"
],

there is no way to reliably determine path to project's autoload.php. Therefore, the tool doesn't work with command line applications.

Seems either we find a way to solve the problem or find out another workflow that suits it better.

If a developer did not setup SSH key for Github account, installation fails.

[email protected]: Permission denied (publickey).

Error message is quite confusing.

I do not have access to my own repo with fork? But why? It is mine, why do I have no permissions?

Requirement to set up SSH key before installation is not obvious.

I suggest that tool should check access to repo before taking any action.

With SSH key:

Checking access to "user/fork-name"... OK
Cloning "user/fork-name"...

Without SSH key:

Checking access to "user/fork-name"... DENIED
Seems like you have not installed SSH key to you Github account.
Key is required to work with repository via SSH.
See here for instructions: https://docs.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account

There is no need to check access every single time. Just check when repository is cloned first time, it should be enough.

Currently only exec command output is directly outputted into console. The rest of the commands, such as update, are waiting till completion.

It should fail if:

1. minimum-stability is set to "dev", "beta" or "alpha".
2. Any @dev packages present.

1. Add "psr/container": "^1.0", to composer.json to any package.
2. Run fix-dependencies.

Expected to see psr/container removed. Actually getting "Nothing to fix" message.

Command ./yii-dev install [<packages>] can automatically set upstream for repository forks. It's can be achieved by internal execution of git command git remote add upstream https://github.com/yiisoft/<repository>.git.

For those developers who use forks, this would eliminate most of the routine when setting up the environment.

Currently that's not a fast process for a contributor.

Ability to generate quality report for a package will help us keeping things in order.

Here's some ideas:

1. Package dependency graph: https://github.com/clue/graph-composer
2. Instability/abstraction graph: https://pdepend.org/screenshots.html

Commands logic is getting bigger and harder. At the same time, we are building more and more console "bicycles". We can replace our console components with Symfony ready-made components to simplify development.