Community
Participate
Working Groups
Current implementation of Resource#isConflicting is not symmetric as it should be if we use multi-rule. For a project with two folders a and b we get the following results: multi = MultiRule.combine(a, b); a.isConflicting(multi); => false but should be true multi.isConflicting(a); => true Patch will follow.
Created attachment 205691 [details] Patch v1
You could just do something like this: if (rule instanceof MultiRule) return rule.isConflicting(this);
(In reply to comment #2) > You could just do something like this: > > if (rule instanceof MultiRule) > return rule.isConflicting(this); True. I just wanted to keep the order of the arguments unchanged when calling subsequent #isConflicting. If we switch the order, it can be hard to debug further enhancements (like bug 254948).
Created attachment 205732 [details] Patch v2 Adjusted to comment 2.
Looks good.
And that was a good find! Thanks for tracking this down.
Shall I release this for M3?
Assuming all core resource tests pass, go for it.
Thanks! Fixed in master.