From 0895268df2b186b3d93af9877d5b036c95dbc443 Mon Sep 17 00:00:00 2001 From: Damien De Paoli Date: Fri, 26 Sep 2025 19:20:47 +1000 Subject: [PATCH] more thoughts on change over to json, etc --- TODO | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/TODO b/TODO index 22033be..0c073f4 100644 --- a/TODO +++ b/TODO @@ -8,6 +8,7 @@ * client side always has query_id. IF DB does not have query_id, then its really old? - just say so... * client side takes query_id, entry_lst, current_eid, offset, first/last_eid, etc. as part of its first route / html creation. + * get this data as a json blob? or ask chatgpt to see how best to take the data and turn it into jscript data * it then decides based on all this to GetEntryDetails( subset of entry_lst ) <- needs new route * IN THEORY some of the subset of entry_lst don't exist -- BUT, we can handle that on response, e.g. say my query used to have 1,2,3, and since then another user/action deleted 2: - I ask for details on 1,2,3 and get back details on 1,3 only. @@ -21,6 +22,10 @@ - When job that flips, rotates, deletes completes then lets update the query details (e.g. remove eids, or remove the ammendments) - this actually is quite an improvement, if someone is deleting 2 as per above, I will see that as a pending change in my unrelated query, ditto flips, etc. + * NEED to work through how we deal with directories when we do the json data versions above? + - e.g. does entry_list only contain files? OR filter the details in the jscript? + - how do we do dirs in this context? (when folders=True) + ### GENERAL * jobs for AI should show path name * rm dups job should show progress bar