frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

added a question about the design for the attention of @knolleary

ly685 2014-08-19 16:11:52 -07:00
parent 56c20df4dc
commit 9dcd06c9a6
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
dynamic-palette.md

@ -38,3 +38,9 @@ To remove a node from the palette:
2. If the any of the corresponding nodes are in use, the request is rejected 2. If the any of the corresponding nodes are in use, the request is rejected
3. The runtime registry removes the corresponding nodes. 3. The runtime registry removes the corresponding nodes.
4. An event is fired over the comms link telling any connected editors that the nodes have been removed. 4. An event is fired over the comms link telling any connected editors that the nodes have been removed.
### Question
@knolleary : Ref the point about multiple nodes:
- a node file or module can contain multiple nodes. Making a request to remove a single node type may trigger the removal of multiple node types.
Is it possible to have two options? One to remove a specific node and a second to remove the collection? I am thinking of a use case where a Node module contains (for instance) 5 nodes for a specific use case (e.g, home automation), and I want to/will regularly use 3 of those nodes in the bundle but not interested in 2 of them. Can I just remove the 2 nodes to have a cleaner palette and runtime?
<ly> PS: This section can be removed when dealt with </ly>