Going 1.0 about nitrocli HOT 2 OPEN

There is one more thing I have been thinking about on and off, and that is error reporting. We do a reasonable job in general, but what may be considered missing is more context. For example, when looking up an extension we may get an io::Error and all it says is "file not found". Without context (and there is little aside from the command being invoked [which may be enough in the example but not in general]), this error may or may not be helpful.

I believe that crates such as error-chain (and I believe fault at some point, but I can't find off hand), provide some more useful context in a generic way. We may want to consider evaluating those to up our game.

from nitrocli.

There is also custom_error that I just came across. But ultimately we may just stick to what we have. If we ensure a little more context for all errors that don't already have it (most nitrokey reported errors do by virtue of the get_error function) we should be good. And that can probably be enforced statically at compile time.

from nitrocli.