-
Notifications
You must be signed in to change notification settings - Fork 46
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
Extract user deletion into a new service #919
Conversation
Just spotted cc @FCsongradi |
Introduce a programming API for downstream developers that allows customizing what should happen when a user is deleted in Drupal. Co-authored-by: Dezső BICZÓ <[email protected]>
*/ | ||
interface UserRemovalHandlerInterface { | ||
interface PostUserDeleteActionPerformerInterface { |
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.
Is is better? I mean, naming is hard... but I think it is better to be explicit and descriptive in names (in domain driven style) when designing public APIs. If we like this I can squash this change to other commits.
* {@inheritdoc} | ||
*/ | ||
public function __invoke(UserInterface $account): void { | ||
($this->decorated)($account); |
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.
Double checked and this was the original order as well, the hook in apigee_edge was called sooner than in this module - which makes total sense.
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.
Checked for Apigee Edge and X both.
LGTM
* Extract user deletion into a new service Introduce a programming API for downstream developers that allows customizing what should happen when a user is deleted in Drupal. Co-authored-by: Dezső BICZÓ <[email protected]> * Leverage the new user removal handler API for cascade deleting team roles * Better naming for the new API and implementations --------- Co-authored-by: ferenc.csongradi <[email protected]>
* Extract user deletion into a new service Introduce a programming API for downstream developers that allows customizing what should happen when a user is deleted in Drupal. * Leverage the new user removal handler API for cascade deleting team roles * Better naming for the new API and implementations --------- Co-authored-by: Dezső BICZÓ <[email protected]>
Introduce a programming API for downstream developers that allows customizing what should happen when a user is deleted in Drupal.
Co-authored-by: @FCsongradi
Closes #915