Some further observations from logs, including Lazy Plugin Loader

Author: SebastianMC

docs/tech/initial-auto-sort-and-notifications.md

@@ -35,26 +35,29 @@ Additional remarks:
 
 ## Design
 
-0. Before all, capture the sequences of key execution points and events (related to #161)
+Before all, capture the sequences of key execution points and events (related to #161)
 
-1. Fine-grained recognition of states of involved elements:
-  - non-epmty sorting spec present or not?
-  - sorting spec parsed successfully, hence ready to be applied?
-  - File Explorer view available?
-    - patchable?
-    - lazy view?
-  - plugin load time?
-  - ...
+Log below shows some unexpected edge cases and sequences of events, e.g. Lazy Plugin Loader, when
+  the metadata-cache-populated event never reaches the plugin
+
+Is it possible / feasible to both:
+- handle the optimistic scenario of auto-sorting on start on the first display of File Explorer? AND
+- gracefully handle the delayed scenario, e.g. Lazy Plugin Loader or for whatever reason?
+
+The delayed scenario, should be handled with a popup and explicit user confirmation
+- can this scenario be indeed correctly recognised and not confused with other scenarios
+  in which the automatic sorting should not be applied?
 
 ---
 Log
 
 Things turn out to be trickier than I expected.
 
 Sample logs generated by current log-decorated version:
+
 ```
 Scenario: File Explorer hidden on close, automatically hidden on start:
-On end: File Explorer invisible, ribbon indicated 'sorting not applied'
+On end: File Explorer invisible, ribbon indicated 'sorting not applied, enabled'
 c-s ep: (b pre-1) entered patchFileExplorerFolder()
 c-s ep: (a pre-1) entered checkFileExplorerIsAvailableAndPatchable()
 c-s ep: (a pre-2) this.getFileExplorer ok
@@ -117,3 +120,15 @@ c-s ep: (f) patched getSortedFolderItems invoked!
 c-s ep: (f) patched getSortedFolderItems invoked!
 ```
 
+```
+Scenario: FE visible, sorting enabled, custom-sort plugin delayed via Lazy Plugin Loader
+On end: File Explorer visible and not sorted, ribbon indicates 'sorting enabled but not applied'
+
+c-s ep: (b pre-1) entered patchFileExplorerFolder()
+c-s ep: (a pre-1) entered checkFileExplorerIsAvailableAndPatchable()
+c-s ep: (a pre-2) this.getFileExplorer ok 
+c-s ep: (a pre-3) has requestSort()
+c-s ep: (a) 1.6.0+ and has getSortedFolderItems()
+c-s ep: (f pre-1) patched getSortedFolderItems factory!
+c-s ep: (b) 1.6.0+ and patched getSortedFolderItems()
+```