frodovdr
/
node-red
mirror of https://github.com/node-red/node-red.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Design: Palette Management UI (markdown)

Nick O'Leary 2016-08-09 23:55:30 +01:00
parent 83577ab447
commit 7f4fb70895
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Design:-Palette-Management-UI.md

@ -104,7 +104,7 @@ By default, the catalog will be one we provide. But it needs to be possible cust
A use case for providing a custom catalogue is to provide a smaller curated list of nodes - but still picked from the nodes that are publicly available. That will work with the current design where the module passed over the runtime api is assumed to be npm installable from npmjs.org.
Another use case is to provide a catalogue of nodes from an alternative npm repository. In that instance, the catalogue must also provide sufficient information to allow the runtime to target that repo when running the npm install.
Another use case is to provide a catalogue of nodes from an alternative npm repository. In that instance, the catalogue must also provide sufficient information to allow the runtime to target that repo when running the npm install. The runtime api will need to be updated to support this case.