xible - npm Package Versions

[0.13.0][] - 2018-06-05

Added

• The commandline xiblepm nodepack upgrade can now be used to upgrade all installed nodepacks in one go. (#42)

• The commandline xiblepm nodepack update has been introduced as an alias for xiblepm nodepack upgrade.

• All xiblepm commands that interact with the registry now support the optional --registry parameter. You can use this to deviate from the default registry stored in your config file.

• Implemented commandline xible server stop to stop a running XIBLE server. (#76)

• Support for textareas in node editor contents. (#75)

• Added several string nodes such as string.replace. (#74)

• The editor now keeps track of all messages shared by nodes. To save space in the editor, the resource graphs and this new log functionality share the same area and can be toggled. (#63)

Changed

• Flow instances that exited on their own, no longer auto start when XIBLE restarts.

[0.12.0][] - 2018-05-13

Added

• Nodes can now host their own routes through the API of XIBLE. Have a look at the new routes documentation on how to use them. (#71)

• Starting a flow through the editor which uses xible.flow.param nodes will now request for the values of those parameters. (#57)

• NodeOutput triggered functions can now return promises instead of relying on the callback parameter. (#73)

Changed

• Hexadecimal colors are now allowed in typedefs.

• object.assign node works on all target inputs, instead of just the first one.

• Saving or deploying a flow while instances on it are running, prompts the sure to ensure it is okay that these running instances are stopped. (#38)

• Starting while instances are already running prompts the user to stop the running instances or leave them running.

• The xible.flow.param node has been renamed to xible.flow.instance.param. The parameter (value) is assigned and therefore specific to the instance, not the flow.

Fixed

• cast node is working again now the output type is properly reset when all connectors detach.

• Installing a nodepack through the editor now properly reloads the typedefs. This ensures that the colors on inputs & outputs are working, and that connectors work across the inheritance chain of a newly added typedef.

• Flow instances stop if there is no more work to be done. Also, XIBLE exists properly after calling xible.close().

[0.11.1][] - 2018-04-28

Added

• TypeDef API route test cases.

Fixed

• The store node is working again now the input and output types are set properly.

• When the Flow initialization level is set to 1 (Flow), the pre initialized instance is now spawned correctly when saving/updating flows.

• Typedefs are properly checked on existance when multiple nodepack paths are initialized.

• Deleted flows no longer re-appear in the editor after the connection to the XIBLE server reconnects.

[0.11.0][] - 2018-04-23

Added

• Added several shortcuts for xiblepm user * command line commands. (#67)

• Alternative panning support without a scroll wheel by holding down shift and the left mouse button. (#59)

• Use ctrl to combine multiple area selectors in the editor. (#69)

Changed

• Improved xiblepm user add registration process. (#65)

Fixed

• Individual password characters are no longer briefly visible on the windows command line. (#66)

• Fixed potential XSS attack concerning flows downloaded from the registry where the nodes were not installed on the target machine.

• input.duplicate node with amount of duplicates set to '1' would throw 'already called back'. (#68)

• Installing nodepacks from the registry through the editor works again. (#70)

[0.10.0][] - 2018-04-08

Added

• Added the xible.flow.param node including applicable command line and REST API options. These allow parameters to be send when starting a flow. (#45)

• A flow can now be instantiated multiple times. (#46)

• Added input.* nodes to modify return values. (#48)

• Implemented xible service restart command to restart the xible service if it was installed. (#51)

• Connection status messages are now visible on every view. (#52)

Changed

• xible.flow.start raises an error if a flow does not exist.

• xible.flow.start contains an output for the instance it created when starting a flow.

• If the extends keyword for a typedef is not set, it defaults to object.

• NodeOutputs that do not have a type set, will no longer be triggered to ensure only values within the extends chain of the calling NodeInput are returned. (#49)

Fixed

• Configuring SSL now redirects plain HTTP requests to the configured SSL port, instead of plain HTTP port + 1.

• The node help page now properly shows the original (structure) type of the node inputs and outputs, instead of the active type.

0.9.4 - 2018-04-03

Fixed

• The editor is working again properly after including the shrinkwrap which points to the right xible-wrapper version. (#61)

[0.9.1][] - 2017-12-20

Fixed

• xible service install is working again. (#43)

• npm start from the XIBLE directory is working again.

• Navigating the settings page properly uses async requests again instead of reloading the entire page.

[0.9.0][] - 2017-11-01

Added

• Within the editor, optional input fields are now hidden unless the containing node is either hovered or selected. (#36)

• The xible command line interface now supports the 'node' context for getting and setting data values on nodes. (#34)

• Add a 'state' output to the xible.flow node. This returns the running state of a flow, a number between 0 and 5, inclusive.

• Implemented xiblepm nodepack remove for removing nodepacks. (#24)

• Implemented xiblepm nodepack upgrade for upgrading nodepacks. (#41)

Changed

• Instances of Node only receive a trigger event when they are an event node at the start of a flow. Previously, this event would also be emitted whenever an input trigger was hit.

Removed

• document.* nodes are removed, after they were deprecated in favor of object.*.

• xiblepm flow remove is removed after it was deprecated in version 0.7.0. It was replaced by xible flow delete.

Fixed

• Long uninterrupted strings in node descriptions would overflow the node selector.

• Performance of node selector has been greatly improved, especially when there are many nodes installed.