refactor: split up cli subcommands into their own modules

DHARPA-Project · Jun 17, 2021 · 5ac887b · 5ac887b
1 parent d48d66b
commit 5ac887b
Show file tree

Hide file tree

Showing 19 changed files with 901 additions and 707 deletions.
diff --git a/.editorconfig b/.editorconfig
@@ -0,0 +1,2 @@
+[*.md]
+ij_any_wrap_long_lines = true
diff --git a/docs/architecture/data/storage.md b/docs/architecture/data/storage.md
@@ -0,0 +1,7 @@
+# Data storage
+
+This is a document to describe my plans for storing data (and metadata) in *kiara*. (Almost) nothing I describe here is inmplemented yet, so it only reflects my current thinking. I think the overall strategy will hold, but there might be changes here and there.
+
+## The problem
+
+*kiara*s main functionality centers around transforming input data sets to output data sets. Those outputs need to be stored, to be of any use later on. Obviously. When deciding how to do this, we must take into account concerns about performance, disk- and memory-usage, data versioning, which metadata to attach, in what way, how to deal with metadata schemas (and versioning of both), etc.
diff --git a/setup.cfg b/setup.cfg
@@ -55,7 +55,7 @@ console_scripts =
     kiara = kiara.interfaces.cli:cli
 kiara.modules =
     pipeline = kiara.pipeline.module:PipelineModule
-    metadata.extract_python_class = kiara.modules.metadata:ExtractPythonClass
+    metadata.python_class = kiara.modules.metadata:ExtractPythonClass
 
 [options.extras_require]
 cli =