According to the documentation the Service emits an event named "error" in case of errors but it never does, it only logs the one possible error where the service name collides with another service in the network.
|
console.log(new Error('Service name is already in use on the network')) |
The original implementation did emit an error in that case, see here:
https://github.com/watson/bonjour/blob/bdc467a4f3c7b9fe8bc54468b6fc4d80b8f1c098/lib/registry.js#L47
So whenever an error occurs, due to name collisions, a consumer cannot detect it using the API.
Is that behavior intended?
According to the documentation the Service emits an event named "error" in case of errors but it never does, it only logs the one possible error where the service name collides with another service in the network.
bonjour-service/src/lib/registry.ts
Line 35 in 30abed0
The original implementation did emit an error in that case, see here:
https://github.com/watson/bonjour/blob/bdc467a4f3c7b9fe8bc54468b6fc4d80b8f1c098/lib/registry.js#L47
So whenever an error occurs, due to name collisions, a consumer cannot detect it using the API.
Is that behavior intended?