Change reaction-rule config to save the event as: events => { event_name => { array of event settings } }. This needs adaptions in tests, config entity and in the config schema.

Pull request

Comments

a.milkovsky created an issue. See original summary.

a.milkovsky’s picture

Issue summary: View changes

Added PR

a.milkovsky’s picture

Assigned: a.milkovsky » Unassigned
Status: Active » Needs review

Done. See PR in the description

fago’s picture

Status: Needs review » Needs work

thanks, looks good - but:
- there are some test fails: https://travis-ci.org/fago/rules/jobs/109316083
- found a small coding style issue, see PR

a.milkovsky’s picture

Status: Needs work » Needs review

Thx, fixed that

klausi’s picture

Status: Needs review » Needs work

left one minor comment in the PR and you need to merge in changes from 8.x-3.x to resolve the conflicts.

a.milkovsky’s picture

Status: Needs work » Needs review

Thx, fixed PR, resolved the conflicts

klausi’s picture

I think we should stop using arrays and use a class with named properties/methods to be more self documenting what is available and can be used for an event configuration.

fago’s picture

While I agree with that, I don't see how we could do that right now? #2100549: Plugin factories needlessly restrict configuration to arrays is not resolved, and event plugin configuration depends on the event plugin anyway?

fago’s picture

I see, you do not mean plugin config but $rule->events. I've commented on that over at https://github.com/fago/rules/pull/405/files#r53568608.

klausi’s picture

Status: Needs review » Reviewed & tested by the community

Looks good, we can do a follow-up for that.

fago’s picture

Status: Reviewed & tested by the community » Needs work

tests failed now after merge

a.milkovsky’s picture

Status: Needs work » Needs review

I see, expression logic was changed. Fixed it

fago’s picture

Status: Needs review » Fixed

thx, merged.

Status: Fixed » Closed (fixed)

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