v0.0.3
Change Log
New Feature:
- introduces output treatment for schema and procedure
- user can configure output given by schema and procedure respectively
- a bit of color for each output treatment
Bug Fix:
- bug caused by multiple definitions set within a single framework
Reworked Feature:
- framework output is now replaced by output teatment in each schema and procedure
- 'dir' I/O is replaced by 'explorer' for more generic path exploration
- validator and evaluator now handles how to write output, depending on the treatment
Refactor:
- change progress type from 'simple' and 'verbose' to 'iterative' and 'progressive' respectively
- simplify Loader in
core
package to be more readable and easier to maintain - simplify Execute method in Pipeline to be more readable and easier to maintain
- resource is now loaded only when needed to reduce memory consumption
Concept:
- error is divided into two state: execution error and business error
- execution error is thrown if there's any anomaly outside business, such error when reading file
- business error is thrown only if execution does not meet business specified by the user, such as schema execution result
Documentation:
- updated to follow the latest changes