From 30821357aab752f351e50dc9d311a829ceff1ae6 Mon Sep 17 00:00:00 2001 From: Tim Otten Date: Fri, 28 Sep 2018 16:02:10 -0400 Subject: [PATCH] roadmap.md - Add tidbits --- ext/afform/docs/roadmap.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/ext/afform/docs/roadmap.md b/ext/afform/docs/roadmap.md index a0a9f08038..c970475f30 100644 --- a/ext/afform/docs/roadmap.md +++ b/ext/afform/docs/roadmap.md @@ -39,4 +39,9 @@ Within this extension, there are things which need updating/addressing: * The data-storage of user-edited forms supports primitive branching and no merging or rebasing. In an ideal world (OHUPA-4), we'd incorporate a merge or rebase mechanism (and provide the diff/export on web+cli). To reduce unnecessary merge-conflicts and allow structured UI for bona-fide merge-conflicts, the diff/merge should be based on HTML elements and - IDs (rather than lines-of-text). \ No newline at end of file + IDs (rather than lines-of-text). +* API Request Batching -- If a page makes multiple API calls at the same time, they fire as separate HTTP requests. This concern is somewhat + mitigated by HTTP/2, but not really -- because each subrequest requires a separate CMS+CRM bootstrap. Instead, the JS API adapter should + support batching (i.e. all API calls issued within a 5ms window are sent as a batch). +* Default CSS: There's no mechanism for defining adhoc CSS. This is arguably a feature, though, because the CSS classes + should be validated (to ensure theme interoperability). -- 2.25.1