petty greivance if that's the accepted means, but here a thing...
my team has a pattern of indicating a failure state by raising exception that isn't caught, flows out to the ncs wrapper running a given callback, which causes whatever message put upon the exception to output in the cli (and I presume be included in a response body or error field via restconf, dunno yet).
Question: is there a way to SIGNAL to ncs that an error state was found - and to return with a message in that state, versus throwing an exception at the sky the way we currently do?
I can't find anything about such, so it might be the recommended way to just to throw.
if so, I'll probably rework the returns to something that can assure consistency in formatting across codebases and then throw that... but I'd rather tell the user 'no, logic error, details' in a manner that does not involve creating an exception class instance and inducing crash-like perspective. I want to be able to see instances of exception of type as valid of system in failure, versus user input of logical error. i suppose I can type them differently.... but I'm going in circles...
can you signal and return from a callback explicitly (no, i failed, here's why, details. return that to the user with status code 123??) - rather than invoking language panic/stacktrace gather/otherwise expensive behaviors?
