We're planning on splitting up the framework into an NPM module which will be pulled in by appropriate bots. Given that, how do we ensure that this works properly? Probably the most sensible is a 'constructor' for the ProcBot super class that includes information to use, and then ensure the framework uses resin-corvus if the relevant details exist.
@hedss let's hold off at least till tomorrow's arch call to get a final decision on resin-corvus vs some-other-analytics-and-error-tracking-consolidated-lib
We're planning on splitting up the framework into an NPM module which will be pulled in by appropriate bots. Given that, how do we ensure that this works properly? Probably the most sensible is a 'constructor' for the ProcBot super class that includes information to use, and then ensure the framework uses
resin-corvus
if the relevant details exist.