Updated Design: Palette Management UI (markdown)

Nick O'Leary 2016-08-09 23:41:28 +01:00
parent 88330fc804
commit 83577ab447
1 changed files with 6 additions and 0 deletions

@ -100,5 +100,11 @@ By default, the catalog will be one we provide. But it needs to be possible cust
]
}
### Further considerations
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.