From aecd9d0c842fddd7bda37dd251e6cc2fe50d26f8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niels=20Lyngs=C3=B8?= Date: Fri, 3 Jun 2022 12:38:29 +0200 Subject: [PATCH] more notes to remember --- src/Umbraco.Web.UI.Client/src/mocks/data/content.data.ts | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/Umbraco.Web.UI.Client/src/mocks/data/content.data.ts b/src/Umbraco.Web.UI.Client/src/mocks/data/content.data.ts index d41097a685..414b62e466 100644 --- a/src/Umbraco.Web.UI.Client/src/mocks/data/content.data.ts +++ b/src/Umbraco.Web.UI.Client/src/mocks/data/content.data.ts @@ -26,6 +26,13 @@ export interface NodeProperty { tempValue: string; // TODO: remove this - only used for testing } +/* TODO: +Consider splitting data into smaller thunks that matches our different stores. +example: we need an entity store for things in the tree, so we dont load the full nodes for everything in the tree. +We would like the tree items to stay up to date, without requesting the server again. + +If we split entityData into its own object, then that could go in the entityStore and be merged with the nodeStore (we would have a subscription on both). +*/ export const data: Array = [ { id: 1, @@ -50,7 +57,7 @@ export const data: Array = [ }, ], /* - // Concept for stored values, better approach for variants, separating data from structure/configuration + // Concept for stored values, better approach for variants, separating data from structure/configuration, still needs structure for variants. (We could actually split it up so we have each variants data through a separate end-point?) data: [ { alias: 'myHeadline',