-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Drush commands for workspaces - #5933 #5934
base: 13.x
Are you sure you want to change the base?
Conversation
return; | ||
} | ||
|
||
$workspace->publish(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this fails with wse enabled, because \Drupal\wse_preview\Negotiator\CookieWorkspaceNegotiator::unsetActiveWorkspace
tries to get the user session
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll look into this asap :)
#[CLI\Command(name: 'workspaces:publish')] | ||
#[CLI\Argument(name: 'id', description: 'The workspace to publish.')] | ||
#[CLI\Usage(name: 'workspaces:publish stage', description: 'Publish the stage workspace')] | ||
public function commandName($id) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to ensure that the module is enabled: #[CLI\ValidateModulesEnabled(modules: ['workspaces'])]
This needs Drush test coverage. I think an integration test will fit well. As setup the command would create a workspace, make it active, create a node in the workspace, run the drush command, and ensure the node is now published. |
Aims to fix #5933