From 7f4fb70895d302ddebaca091f65ebdbd86b72124 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Tue, 9 Aug 2016 23:55:30 +0100 Subject: [PATCH] Updated Design: Palette Management UI (markdown) --- Design:-Palette-Management-UI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Design:-Palette-Management-UI.md b/Design:-Palette-Management-UI.md index b87ea49..fcdc6a1 100644 --- a/Design:-Palette-Management-UI.md +++ b/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. \ No newline at end of file