mockDOMSource can't mock events for isolated nested components

[m-orchard]

There isn't a way to differentiate events mocked with mockDOMSource, where nested components are listening to events on the same namespace and relying on isolation to differentiate them.

For example, something like: https://jsfiddle.net/25a74k0k/.

The only way I can think to achieve this, is to pass in a custom class to the child (made unique by the parent), add it to the elements being listened to, and then use that custom class when selecting them. However, this is complicating the way a child must be initialised and basically duplicating what we are getting from isolate on the real DOMSource.

Also, in cases where :root is the only selector used, the child would have to wrap the root element in another element to be able to select the custom class, which bloats the mark up.

[m-orchard]

I should mention, I've not had any ideas on how to solve this yet :) it may simply force isolation to be implemented in or copied to mockDOMSource, but I'm hoping someone has a better idea.

[chadrien]

That's a tricky one. I have no idea how we could get past this, but what I know for sure is that the implementation should "force" us to be explicit about the fact that we mock events and observables for a nested component, otherwise reading the tests might make no sense to the reader ("why is he mocking a click on selector x? It doesn't event exists.")

[staltz]

Seems like mockDOMSource needs to take isolation into account. Thanks for pointing this out.

[staltz]

Lifting this from priority 3 to 4.

[staltz]

Done in Cycle DOM v10.1.0