Merge pull request #90 from mapikit/0.3-dev

v0.3 - Mercury Update

CHANGELOG.md

@@ -1,4 +1,26 @@
 # Changelog
+## 0.3.0
+### File Splitting
+- System `schemas`, `businessOperations`, and `protocols` configuration json can now be split into multiple files.
+- The allowed properties can be replaced by:
+  - A string path pointing to a json file of an array of the property type
+  - An array of paths pointing to a multiple files with multiple configurations
+  - A glob pattern that includes those configurations
+  - An array of glob patterns that include multiple configurations
+  - Or a mix of all the above. For more info consult our [documentation](https://mapikit.github.io/meta-system-docs/)
+- Databases are now protocols, allowing for multiple databases to be implemented
+  - MongoDB, previously baked into meta-system, has been separated as its own db protocol: [@meta-system/mongodb-db-protocol](https://www.npmjs.com/package/@meta-system/mongodb-db-protocol)
+- Added a custom logger for meta-system and added debugging to BOps execution flow
+  - This new implementation also comes with logging levels (see below)
+- Improved the meta-system CLI options
+  - Currently the available options are debug, create-log-file, log-level, and type-check.
+  - For more info on those as well as some extra accessory options you can use the --help to option
+- It is now possible to insert arrays directly from the "targetPath" as described in issue #83
+  - Writing it as `targetArray[]` will push the value to an array called `targetArray`
+  - Writing as `targetArray[n]` will insert the value at the specified `n` index
+  - When using a fixed index, you may also insert complex objects. For instance:
+    - `targetArray[2].name` will add an object at index 2 and set the name property to the given value.
+
 ## 0.2.3
 - Fixed bug #64 . The package dependency manager was not handling the case of having multiple installations of the same package if its version was "latest"
 

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="https://user-images.githubusercontent.com/13098424/131416580-f6718c24-5687-4016-8801-44c177a70d42.png">
+  <img src="https://user-images.githubusercontent.com/7462905/213060957-d07b9d24-f7f7-4073-9a61-d030de34f988.png">
 </p>
 
 # Meta-System - A system to be any system

ROADMAP.md

@@ -1,23 +1,23 @@
 # Meta-System Roadmap
 
-## 0.2 - Gemini :heavy_check_mark: 
+### 0.2 - Gemini :heavy_check_mark: 
 - :heavy_check_mark: Support to Function Packages;
 - :heavy_check_mark: Introduces external protocols;
 - :heavy_check_mark: Protocols can provide their BOps functions as well;
 - :heavy_check_mark: BETA - Verification of modules dependency property accesses;
 
-### 0.3 - Future Release
-- Meta-System configuration can be split in multiple files, as long as there is a path declared;
-- Introduces DBProtocols - Databases becomes part of the protocol definition;
-- Schemas need to define a protocol Database to connect to;
-- Add StdOut Debugging capabilities to BOps;
+## 0.3 - Mercury :heavy_check_mark: 
+- :heavy_check_mark: Meta-System configuration can be split in multiple files, as long as there is a path declared;
+- :heavy_check_mark: Introduces DBProtocols - Databases becomes part of the protocol definition;
+- :heavy_check_mark: Schemas need to define a protocol Database to connect to;
+- :heavy_check_mark: Add StdOut Debugging capabilities to BOps;
 
 ### 0.4 - Future Release
 - Streamline CLI usage;
 - Meta-System as a framework - You can create modules locally and use them directly on your Meta-System BOps;
 - Polish Meta-System integration to existing Systems;
 - Add eventful debugging capabilities to BOps - Integrating Meta-System to an existing system should give you the ability to listen to what is happening inside the engine.
-- Verification of module dependecy property accesses - Becoming a stable feature;
+- Verification of module dependency property accesses - Becoming a stable feature;
 
 ### 0.5 - Future Release
 - Meta-System can be run on the Browser;