Robin Krahl's fork of nitrocli https://git.ireas.org/nitrocli/atom?h=output-formats 2020-09-03T04:40:32Z 2020-09-03T04:40:32Z Daniel Mueller deso@posteo.net 2020-09-03T04:40:32Z urn:sha1:888c30e975726260e0af9b61baee6b17c51a06d5 With this change we switch to using a REUSE compliant way of specifying the copyright & license of the program. To be fully in conformance we also add additional license specifications for the remaining files in the project. Lastly, a new CI pipeline rule takes care of verifying compliance on an ongoing basis. 2020-09-02T02:00:31Z Daniel Mueller deso@posteo.net 2020-09-02T02:00:31Z urn:sha1:4686dbf5d79da730776374d7ef3471c3ed4915b5 This change adjusts the copyright header in all files to no longer mention individuals but refer to The Nitrocli Developers in general. 2020-09-03T15:43:05Z Robin Krahl robin.krahl@ireas.org 2020-08-23T14:17:42Z urn:sha1:0cb2ac01371523eae785c12ce88848039090c1e6 Since we moved the model, no_cache and verbosity fields from ExecCtx into Config and added a Config field to both ExecCtx and RunCtx, RunCtx and ExecCtx are identical. Therefore this patch merges the ExecCtx and RunCtx structs into the new Context struct. 2020-09-02T04:20:40Z Robin Krahl robin.krahl@ireas.org 2020-02-02T11:15:27Z urn:sha1:cbd0115cf2d746f5ccde212696376642cee950f9 This patch adds a simple configuration file that demonstrates the syntax and contains some documentation. We suggest to ship this file together with nitrocli and to install it e.g., in the /usr/share/doc/nitrocli directory. This patch also adds a simple test case that makes sure that the example file is parsed correctly. 2020-09-02T04:12:43Z Robin Krahl robin.krahl@ireas.org 2020-01-23T09:54:09Z urn:sha1:3f430bac70a946c776a930fabc5b64a788113452 This patch implements basic configuration handling that reads a configuration file and stores the parsed data in the ExecCtx and RunCtx structs. It supports three configuration items: - model (previously only --model) - no_cache (previously only NITROCLI_NO_CACHE) - verbosity (previously only --verbose) 2020-09-01T02:25:48Z Daniel Mueller deso@posteo.net 2020-09-01T02:25:48Z urn:sha1:98b36813b2ce7789da5981920b672daa47be1c35 In the past we were using an application global custom Result type definition. This makes less sense now that we switched over to using anyhow's Error and Result types. We kept that for the time being, but with this change we remove the type and use anyhow::Result instead. 2020-08-29T01:44:45Z Daniel Mueller deso@posteo.net 2020-08-29T01:44:45Z urn:sha1:592d1a55f0c05c1dcba58261f327066b4832a703 This patch changes our error handling approach from the ground up: instead of having a globally used Error enum that contains variants for all possible errors, we now use anyhow's Error type. This approach is more dynamic (and not statically typed), but it allows for more fine grained error messages and overall more user-friendly error reporting. Overall it also is a net simplification. While we have one dynamic cast now, in order to be able to handle erroneous password/PIN entries correctly, that is considered a reasonable compromise. 2020-07-10T02:01:52Z Daniel Mueller deso@posteo.net 2020-07-10T02:01:52Z urn:sha1:0328fc29bc56498e2312b68e04db828dd1186d23 This change wraps up the removal of the UnwrapError test trait. This step prepares us for the subsequent removal of the application's global Error enum type, in favor of the usage of anyhow's Error type. 2020-07-10T01:57:18Z Daniel Mueller deso@posteo.net 2020-07-10T01:57:18Z urn:sha1:76dfd27ef163f44ef45688bf9d23332c822221dc This change marks the next step in getting rid of the UnwrapError test trait. Specifically, it removes its unwrap_lib_err method. 2020-07-08T16:16:56Z Daniel Mueller deso@posteo.net 2020-07-08T16:16:56Z urn:sha1:eb4419bfd990f0abe75e5e7c248fe1e7efa0843a With upcoming changes we intend to move towards a model where we do not distinguish the individual error variants the program deals with in a global enum. In preparation of such a change, this patch marks a first step in removing the UnwrapError test trait, which relies on the existence of exactly such typed errors. In particular, we remove the unwrap_str_err method from it, basically falling back to just working with strings.