nusje2000/composer-monolith

Provides commands to validate dependencies within a monolithic repository structure

composer-monolith's Issues

Add referenced by to version constraint question in autofixer

This is the current question:

What version of "symfony/security" would you like to require (referenced as [^3.3, ^1.1]) ?

It would be nice if the package referencing the version is displayed as well:

What version of "symfony/security" would you like to require (referenced as [internal/package-1: ^3.3, internal/package-2: ^1.1]) ?

Add default version to version-equalize instead of listing all the different versions

Instead of this:

Equalizable dependency on symfony/symfony (references: package/1: ^4.4, package/2: ^4.4, package/3: ^4.4, package/4: ^4.3)

Do this:

Equalizable dependency on symfony/symfony (references: default: ^4.4, package/4: ^4.3)

Remove dev-only check

The behaviour of this check is not expected. i.e. when you define a package the is only used in development, it makes sense to define the dependencies as require instead of require-dev.

Add current version to VersionConstraintViolation

Change the version constraint message to:

Dependency on "<dependency>" in package "<package>" requires version that matches <version>. (installed: <version>)

update composer-monolith for symfony 6.x

update symfony/console 6.x

Set replace in root definition for internal packages

See: https://github.com/symfony/symfony/blob/master/composer.json

In a composer.json you can set replaces for packages that the defined packages replaces. Within a monolithic repository usually the replace is defined for each internal package. See symfony for example, you could require each component individually, or you could require symfony/symfony.

There should be a new Rule that checks if an internal package is registered and there should be an autofixer that can fix this problem automatically (thus adding a package to the replace and setting the version to self.version).

Rename Validator::validate() to Validator::getErrors()

Use an AST to validate use statements

nusje2000/phpstan-monolith uses PHP Stan to validate use statements in source code based on the composer.json, but this currently has a few limitations:

• It is build with PHP Stan so the error's cannot be fixed automatically with an autofixer
• PHP Stan is significantly slower when using the extension
• Errors can be confusing to read since one missing package can lead to hundreds of errors
• Due to the caching that phpstan uses, updating the composer.json will not resolve the errors because the cached errors are shown

This should not be difficult to achieve using the nikic/PHP-Parser package.

This should also come with a feature to generate a baseline for the errors that occur to be fixed later.

Read replaces from composer json and use this to validate required packages

Example:
symfony/contracts replaces symfony/cache-contracts, symfony/event-dispatcher-contracts, symfony/service-contracts, symfony/translation-contracts

This should mean that when symfony/cache-contracts is required, symfony/contracts will fulfill this requirement.

Add codeowners generator to composer-monolith command