From dd8226ff4ca35a8f1094bd47f8fc4827f437c91b Mon Sep 17 00:00:00 2001 From: zadam Date: Wed, 28 Jun 2023 21:33:09 +0200 Subject: [PATCH] comment --- src/public/app/services/froca_updater.js | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/public/app/services/froca_updater.js b/src/public/app/services/froca_updater.js index 65af4915f..f8ea413d0 100644 --- a/src/public/app/services/froca_updater.js +++ b/src/public/app/services/froca_updater.js @@ -56,6 +56,11 @@ async function processEntityChanges(entityChanges) { } } + // froca is supposed to contain all notes currently being visible to the users in the tree / otherwise being processed + // and their complete "ancestor relationship", so it's always possible to go up in the hierarchy towards the root. + // To this we count: standard parent-child relationships and template/inherit relations (attribute inheritance follows them). + // Here we watch for changes which might violate this principle - e.g. introduction of a new "inherit" relation might + // mean we need to load the target of the relation (and then perhaps transitively the whole note path of this target). const missingNoteIds = []; for (const {entityName, entity} of entityChanges) {