From adcb746bcee2b214515f3f776731912242e3f632 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Sat, 13 Aug 2016 00:38:22 +0100 Subject: [PATCH] Updated Design: Palette Management UI (markdown) --- Design:-Palette-Management-UI.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Design:-Palette-Management-UI.md b/Design:-Palette-Management-UI.md index fcdc6a1..fe737d8 100644 --- a/Design:-Palette-Management-UI.md +++ b/Design:-Palette-Management-UI.md @@ -107,4 +107,9 @@ A use case for providing a custom catalogue is to provide a smaller curated list 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 +### To do + + - [ ] handle load errors on catalogue - 404/timeout/malformed + - [ ] after catalogue is loaded, highlight outdated modules + - [ ] ? catalogue-provided curated lists + - [ ] ? default 'most recent' list