Support for configuring channel / topic delimiter about pubsubjs HOT 3 CLOSED

What would be the benefit, other than aesthetics?

So far, PubSubJS requires no configuration.

from pubsubjs.

Well, for some reasons I like to use "/" as a delimiter instead of ".": One reason ist that I like to switch from another PubSub Library to yours and so I wouldn't have to rewrite all my subscriptions (which right now use "/" as a delimiter). Second reason is that jsdoc has a lot of problems with documenting hierarchical events that use "." as a delimiter. And the third reason is indeed asthetics & also consistency, bc I think a "/" separator is more "logical", since it denotes a "channel" or a "topic" and not a path to an object. If I use this form: "main.sub.subsub" in my code it usually means a path to a javascript object.

By this way, PubSubJS would also be more compatible / exchangable with other solutions, since the actual API is almost the same everywhere, but some solutions use "/" as a delimiter, and others use ".". Of course this kind of configuration should be entirely optional and not required.

from pubsubjs.

Use the fork, Luke!

I really don't see these proposed changes being relevant for the general audience of this tiny library, so I'd rather see another fork of it, than to add to the weight of the library or destabilise it to scratch a very specific itch.

from pubsubjs.