this is a placeholder, someone from the rules maintainers should explain the derivatives policy here in order to allow other modules to write their own rules plugins.

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

What is a derivatives policy exactly?

Anonymous’s picture

Anonymous (not verified) commented

We wrote a lot of plugins for rules using derivers, but didn't discuss this with the maintainers of the other modules integrating with rules because none were at the dev days. Or at least not that I knew. Dasjo suggested we write some documentation explaining the reason for that choice, so that other modules implement their rules plugins the same way. I guess that ticket should go to fago.

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

as far as I can tell, fago said that he did the math and making derivatives based on entity types makes sense.

we will try to get feedback from him for more details :)

fago’s picture

fago
Primary language German
Location Vienna
commented

- Actions/conditions should not be generated per field - that would lead to many
- Actions/conditions should be generated per entity type - that makes a good UX. Category should be the entity type.
- If it makes sense for a use case, entity generic actions/conditions are fine *in addition* to entity-type specific ones
- Actions/conditions should per bundle - is that question. We need generic ones that do not hard-code the bundle also.

For now, let's just go without bundle-specifc actions.

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Active » Fixed

Yes, I think we have issues for remaining tasks to convert actions to derivatives. Closing this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.