Hypen in pubsub topic name breaks delivery

Describe the bug When using this: example.hello topic name, messages get delivered okay. When using this: example-hello topic name, messages do not get delivered.

To Reproduce

"use strict";

// does not work
const topic = 'example-hello';

// does work fine
// const topic = 'example.hello';


const opts = {
    realm: 'realm1',
}
const ws = new Wampy('/ws', opts);
ws.subscribe(topic, function (dataArr, dataObj) {
    console.log('got it', dataArr);

});


const w2 = new Wampy('/ws', opts);
w2.publish(topic, 'hello-foo');

[KSDaemon]

Hi @cameronelliott! I don’t think you noticed that in the documentation:

* **uriValidation**. Default value: strict. Can be changed to loose for less strict URI validation.

And as @gammazero already mentioned, strict validation is preffered. In this case you can safely use any router and client and be sure about interop.

[gammazero]

@cameronelliott

• Yes, applications should use the strict spec. This guarantees them a compatible URI.
• Client libraries may allow both, but a client library could choose to be opinionated about this and decide to restrict to only using strict. This is likely as the library implementer does not want to handle issues arising from someone’s use of a client not working with a router that is configured to only handle strict spec.
• Routers should allow both, but that is a choice and is configurable.