Stop using action in user module in role entity hooks

Open on Drupal.org →

Created on 12 March 2024, 9 months ago

Updated 17 March 2024, 9 months ago

Problem/Motivation

Follow-up for #3413949-38: Move some Action plugins to Action module →

I think for user_add_role_action, user_remove_role_action I think it's worth a follow-up to discuss. i.e. for me it's weird that user hooks call out to actions, user can directly use its own APIs in these cases. But that would be at least one issue to refactor user hooks to not depend on actions, then another to move them, so scope here seems fine.

Steps to reproduce

See user_user_role_insert() and user_user_role_delete()

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task

Status

Active

Version

11.0 🔥

Component

User system →

Last updated about 18 hours ago

Maintained by
🇺🇸United States @moshe weitzman
🇧🇪Belgium @kristiaanvandeneynde

Created by

🇫🇷France andypost

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @andypost
Comment 9 months ago →
🇫🇷France andypost
It may make outdated 🐛 Configured actions created by User module cannot be edited Needs work
Comment 9 months ago →
🇫🇷France andypost
So moderation is only consumer of views and configurable actions?
Comment 9 months ago →
🇫🇷France andypost
Looks this actions are needed only for views' VBO as it was added in #1846172: Replace the actions API →

Locking for config is not yet ready, so naming is a way to not break this automagic 🐛 Cannot edit actions created by user_user_role_insert() Needs work
Comment 9 months ago →
🇫🇷France andypost
This one was a follow-up to make actions more inline with the rules module ✨ Use Context system for actions Needs work

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024