Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Terminus 2.4.0] Conflict with php_codesniffer #1

Open
uberhacker opened this issue Aug 31, 2020 · 2 comments
Open

[Terminus 2.4.0] Conflict with php_codesniffer #1

uberhacker opened this issue Aug 31, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@uberhacker
Copy link
Contributor

In ComposerDependencyValidator.php line 120:

The plugin terminus-plugin-project/terminus-code-plugin has installed the project squizlabs/php_codesniffer: 2.9.2, but Terminus has installed squizlabs/php_codesniffer: 3.5.6. To resolve this, try running 'composer update' in both
the plugin directory, and the terminus directory.

@uberhacker uberhacker added the bug Something isn't working label Aug 31, 2020
@uberhacker uberhacker changed the title [Terminus 2.0.4] Conflict with php_codesniffer [Terminus 2.4.0] Conflict with php_codesniffer Aug 31, 2020
@greg-1-anderson
Copy link

It's easier to install Terminus plugins with --no-dev to reduce the number of dependencies that need to be kept in lock-step.

Terminus support for plugins with dependency is minimal.

@uberhacker
Copy link
Contributor Author

@greg-1-anderson: Thank you for the feedback! Good to know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants