- Some changes in package.json;
- No code changes;
- Fix: Build has an incorect filenames;
- Package.json: "exports" section was added. Allows you to use package as commonjs or es6 module without additional configuration;
- Dev dependencies update. [email protected];
- Bug: Build has an incorect filenames;
- Converted to ES6 module;
- CommonJS and UMD modules are available in dist folder;
- Documentation update, badges, links;
- Fix: Process-step 'set' did not ignore empty strings;
- Breaking change: Hook argument comes as typles. Was: (data,modifier), become: ([data, id], modifier )
- Bug: Process-step 'set' did not ignore empty strings;
- Fix: WatchHook combines results even they are not for extending data record
- Bug: Process-step 'set' did not ignore empty strings;
Version 2.1.x was step in right direction but changes were not enough and software starts to looks incomplete and buggy. Hook functions work on inconsistency way. Hook modifiers were very limited. Manipulation of data is also problematic. Using a configuration for overwrite data/templates/processes is heavy and not flexible enough. So... the new version have:
- Overwrite configuration is completly removed. Now writing methods have attribute method Process-steps have equivalent field method. Method has 4 possible values: - add(default): Add only a non-existing values. Do not change fields that already exist; - update: Overwrite only existing fields. Do not add new records; - overwrite : Overwrite existing record or create new ones; - heap : Combine the old and the new value;
- Hook function execution is per every data-segment. In version 2.0 we have single hook-function execution with all current-data.
- Hook function should always return an array with single element. Data-segment argument is also an array with single element. On this way, you can apply 'modify' function directly on incoming data-segment.
- Hook functions modifiers can execute process-steps [ 'draw', 'block','set', 'alter', 'add', 'copy', 'remove' ]. Don't forget that scope of hook is now only a single data-segment. Hook functions have no access to templates and step alterTemplate is not available. Don't try to use 'hook' inside the hook. We want to keep logic flat as possible. Should be human readable.
- Version 3.0.0 is coming with more than 190 unit tests.
- Bug: WatchHook combines results even they are not for extending data record
- Bug: Process-step 'set' did not ignore empty strings;
- Fix: WatchHook data after 'set' process-step
- Bug: Process-step 'set' did not ignore empty strings;
Read upgrade notes for version 2.1.x.
- Watch-hooks introduction
- Process-step 'save' with
methods
: add/update/heap/overwrite - Process-step 'block' with methods;
- Upgrade webpack to version 4.30;
- Fix: Correct flatten of deep objects;
- Bug: WatchHook data after 'set' process-step
- Bug: Process-step 'set' did not ignore empty strings;
- Fix: method getProcessLib returns JSON representation of intProcess type object. Should be object of extProcessLib type;
- Method 'getTemplateLib' without arguments will return all templates without modification;
- Breaking change: Method 'getProcessLib' returns 'extProcessLib'. Was JSON representation of 'extProcessLib';
- Breaking change: Argument extLib for method 'insertProcessLib' was changed. Was JSON, now is extProcessLib object;
- Bug: Flatten of deep objects is not working as should.
- Bug: Process-step 'set' did not ignore empty strings;
- Run throws console error if any errors
- Bug: method getProcessLib returns JSON representation of intProcess type object. Should be JSON representation of extProcessLib type;
- Bug: Process-step 'set' did not ignore empty strings;
- Process-step 'add' was switched on;
- Readme has link to documentation wiki;
- Bug: method getProcessLib returns JSON representation of intProcess type object. Should be JSON representation of extProcessLib type;
- Bug: Process-step 'set' did not ignore empty strings;
- Process-step 'add' is not active.
- Node.js module;
- Browser module;
- Test package;
- Bug: method getProcessLib returns JSON representation of intProcess type object. Should be JSON representation of extProcessLib type;
- Bug: Process-step 'set' did not ignore empty strings;