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.
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.
Comments
Comment #2
a.milkovskyAdded PR
Comment #3
a.milkovskyDone. See PR in the description
Comment #4
fagothanks, looks good - but:
- there are some test fails: https://travis-ci.org/fago/rules/jobs/109316083
- found a small coding style issue, see PR
Comment #5
a.milkovskyThx, fixed that
Comment #6
klausileft one minor comment in the PR and you need to merge in changes from 8.x-3.x to resolve the conflicts.
Comment #7
a.milkovskyThx, fixed PR, resolved the conflicts
Comment #8
klausiI 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.
Comment #9
fagoWhile 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?
Comment #10
fagoI 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.
Comment #11
klausiLooks good, we can do a follow-up for that.
Comment #12
fagotests failed now after merge
Comment #13
a.milkovskyI see, expression logic was changed. Fixed it
Comment #14
fagothx, merged.