-
Notifications
You must be signed in to change notification settings - Fork 396
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
Drupal console exception #896
Comments
@epfremmer Working on an update here: #887 Unfortunately, an update does not resolve the console issue. |
@grasmash That is super weird. It does look like it changed the error wherein before we had a missing constructor argument (Drupal\metatag\Generator\MetatagGroupGenerator) it changed to a fatal error thrown in MetatagGroupGenerator when it couldn't autoload the Drupal\Console\Generator\Generator class. Its as if drupal/console-core wasn't installed or is missing from the autoloader, but I see composer installing it in the build logs. |
@epfremmer Drupal console was updated in #887. |
@grasmash 👍 thanks again! |
My system information:
When I run this command:
I get the following output:
And I expected this to happen:
normal drupal console command list output
Additional Information:
It looks like BLT is using an earlier version of the drupal/console package. Currently this has a hard version constraint in the blt composer.json locked at 1.0.0-beta5. This in combination with the use of the metatag module produce this exception due to the earlier version of the drupal console instantiating console commands by hand through reflection before they implemented a compiler pass to retrieve them from the service container.
Since the commands included in the metatag module have constructor arguments drupal console is unable to run.
Possible Solutions:
1.0.0-beta5
to something less restrictive like^1.0
to allow console updates as well as more control of the dependency from the project.The text was updated successfully, but these errors were encountered: