We’ve never managed to recreate this issue to get to the bottom On and its z property is set to 0 or "" - causing the node to disappearįrom the editor. We’ve seen a very small number of instances where a node forgets what tab it is the flowFilePretty option is now automatically enabled for projects unless explicitly set to false.the project settings dialog also now lets you edit the project’s version string.Will be automatically committed with every deploy. Option, under User Settings, lets you enable an ‘automatic’ mode where changes The projects feature now provides an option for a simplified git workflow. Nodes, it gives you the option of replacing the instances you already have, In the case of Subflows and Configuration With this release, when you import a flow that contains nodes you already have,
OUR RED STRING DOWNLOAD UPDATE
Update all the instances to the new subflow. Way to do it - it would be imported as a new subflow and you’d have to manually If you wanted to import an update to a subflow you are using, there was no easy
That has generally worked well, but on some occasions it wasn’t ideal. To ones you already had, the editor would avoid importing a duplicate copy and If that flow included configuration nodes or subflows that were identical This meant that if you imported the flow again, you’d get a secondĬopy. In previous releases, when you import a flow, all of its nodes are assigned new If upgrading, please read the upgrade instructions. Node-RED 1.2 is now available to install.
0 kommentar(er)
