You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the fiddle handling the afterAddGroup event, after adding a group and a second rule to that new group, the condition is still seen to be the default, "AND". However, if handling the afterAddRule event and following the same steps, the condition is set to "OR".
The logged new value for condition shows as "OR" in both cases. I've also tried using the model of the group parameter model instead of calling "getModel" in the afterAddGroup handler but the results are the same.
I just thought this was odd, should we not be able to change the new group's condition in afterAddGroup?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
I wasn't sure if this is expected behaviour or not so thought I'd post.
When handling the afterAddGroup event, I noticed that changing the new group's condition seems to have no effect or is overwritten after the event.
I set a up a jsFiddle to show what I mean.
If you run the fiddle handling the afterAddGroup event, after adding a group and a second rule to that new group, the condition is still seen to be the default, "AND". However, if handling the afterAddRule event and following the same steps, the condition is set to "OR".
The logged new value for condition shows as "OR" in both cases. I've also tried using the model of the group parameter model instead of calling "getModel" in the afterAddGroup handler but the results are the same.
I just thought this was odd, should we not be able to change the new group's condition in afterAddGroup?
Thanks in advance!
The text was updated successfully, but these errors were encountered: