Closed rbultman closed 8 years ago
I am not, by any means, even a novice JS user, but it looks reasonable and consistent to me compared to other code in the module.
If the discovery no longer starts by default I'm afraid we will break discovery for existing users of this package. Ideally we would jump the major version of this package, but the green-bean package references this repo via a git URL rather than a version. I will need to do some work to clean up the dependencies before we merge this.
How about I change it so that the discovery starts automatically, but I add functions to start and stop it manually as well? I'm thinking I pass in an optional parameter on creation that, if not present, causes discovery to start. If the parameter is present, it will start or not start discovery based on the value of the parameter.
Either option is great. If you do an optional argument could you make it an object so we can add other options later?
Will do.
Added two functions, startDiscovery and stopDiscovery. This allows for the obvious. The start-up state is with discovery starting so legacy users won't get hosed.
This makes discovery functionality something that must be started. Adds other ERD functionality needed when using the SDK as an appliance.