From fddb8f03a6f65c04ffd44ddbbbdbf72da93846f5 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Mon, 14 May 2018 16:52:47 +0100 Subject: [PATCH] Updated Design: Custom Node admin route handling (markdown) --- Design:-Custom-Node-admin-route-handling.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Design:-Custom-Node-admin-route-handling.md b/Design:-Custom-Node-admin-route-handling.md index 703ec11..e01e763 100644 --- a/Design:-Custom-Node-admin-route-handling.md +++ b/Design:-Custom-Node-admin-route-handling.md @@ -31,6 +31,14 @@ There are a number of ways a user may access these custom routes - each needs a So we can cover a number of the cases via code inspection and url rewriting - but not all. I don't know how common it is for nodes to add custom images - but its possible, so needs to be handled. +#### Changes + + - [ ] add parsing of the node's html content before initial adding to DOM to spot top level `script` and `link` tags and perform url rewriting. + - [ ] add parsing of the node's edit template before adding to the DOM + - [ ] update `$.ajaxSetup()` to rewrite relative URLs + - [ ] provide a utility function, `RED.util.getAdminUrl`, that will do the url mapping. Nodes can then be updated to use this function where needed. + - [ ] add `httpAdminCors` option (to mirror existing `httpNodeCors` option) to allow cross-domain access to the admin runtime api + ### Runtime side With the split, the server side splits into two separate modules: