Channels are not called recursively if the first one is not matched

[BloodyStupidViktor]

If I listen to 'x:y' and I emit to 'x:y:z', my listener won't trigger. However, if I add a listener for 'x:y:z', then both will trigger. Is this intended? I would expect all 'parent' channels to be visited always, regardless of any gaps in the listeners.
What is the purpose of the namespace check in Mediator.publish? It seems to be the cause.

Best regards

[majkel89]

Does not work for me too.
Version 0.9.6 seems to be fine.

[karol-f]

+1

Code responsible for this is

publish: function(channelName){
      var channel = this.getChannel(channelName || "", true);

The "true" boolean changes behaviour in 0.9.8. From comment i can see that it works other way around than I thought - you publish to let say 'chat:message' and subscribe to 'chat:message:received' and get notified.

To be honest previous behaviour of subscribing to 'chat:message' and publishing 'chat:message:received' was better suited to my needs (and looking at comments - for others too).

We can change to var channel = this.getChannel(channelName || "", false); but won't that break other functionality?

[BloodyStupidViktor]

Oh, never thought it might work that way. I even find this behavior a bit strange. 'chat:message:received' is a specific 'chat:message' event and triggering it from any 'chat:message' just seems wrong. I'd expect it to be the other way around.

[pedroetb]

PR send to apply the change commented by @karol-f

About that comment inside the source, I think it's not correct. The publication doesn't propagate from top to bottom, even with that "readOnly" flag set to true. It makes no sense, it works just the opposite way (from bottom to top).

[nicolaslaplume]

👍

[ajacksified]

PR merged