PHP_CodeSniffer | package contains a default rule set

I updated October CMS System with "composer update", but plugins with "php artisan october:update" command.

I found solution on the docs:

IMPORTANT: If you are using using composer do NOT run this command without first making sure that cms.disableCoreUpdates is set to true. Doing so will cause conflicts between the marketplace version of October and the version available through composer. In order to update the core October installation when using composer run composer update instead.

So i set "disableCoreUpdates = true" on the cms config file and works fine. I can update all plugins without to update a system.

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

It's a known issue (if I'm getting your description correctly): https://youtrack.jetbrains.com/issue/WI-52633

Watch that ticket (star/vote/comment) to get notified on any progress.

I had mistakenly run composer install inside the module folder, which installed dependancies for SS in the module itself, and that was conflicting when vendor:publish.

Note to self: Never run composer install inside composer modules, but from the root of the main project where the module is being required.

Pretty simple: you run composer update (which will update the list of packages, and install them), and afterwards you run composer install --no-dev.

Just out of curiosity: this is only done when updating the Docker image. Is there any good reason for this? Why don't you decouple the image and the source code running in that image?

To investigate further I tried to deploy my app directly from my local setup (cloud app deploy), so without using my Github>GCloud Build bridge.

It deployed like a charm so I tried accessing the docs package I initially wanted to add and as the static files in public/docs/ weren't served I added those lines to my app.yaml:

Looks like you are not running php 7.4. and the dependencies installed (here phpunit and PackageVersion) need it. Sometimes composer runs commands hooked on events and if the command fails everything else can fall.

• Delete the vendor folder.
• Delete composer.lock
• Remove the constraint on php 7.4 version in your composer.json
• Run composer update You should be alright

Btw composer manages project dependencies, not php versions installed. If you're starting out in PHP I'd recommend to stick with 7.3 which is widely available. Honestly you don't need the latest syntax additions to the language.

You already mention it in your question, but this recommendation is a SHOULD and not a MUST. If this is the only PSR-1 issue in your entire project: good job!

But your question was: how do other projects go about this?

Global constants, when used incorrectly, are dependency magnets. They introduce coupling and make your code harder to digest. This Q&A is a very good read on why you should move away from them.

Use dependency injection instead (yes, scalar configuration constants are also dependencies).

Symfony-based projects use:

• either YAML (recommended) or XML configuration files to configure the dependency injection container, along with
• environment variables, to set the configuration options specific to each environment in which the application should run. These env vars are defined in environment-specific .env files.

For example, to configure a Database service in a Symfony project you'd create a YAML file that contains:

This was a bug on laravel/lumen-framework, and should be fixed by version 7.0.1: https://github.com/laravel/lumen-framework/pull/1044.