Sync item folders #44
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Make that item folders of foundry also sync with dragonroll items. If necessary, add the feature to dragonroll to add folders to items
I'll start by exploring the codebase to understand how Foundry sync and items work.
Now let me look at the Foundry module side — how snapshots are built and sent:
Now let me look at the Note model, the note route (folder handling), and the existing tests:
Now let me examine the frontend to understand how items are displayed and where folders would fit:
Let me look at the remaining relevant frontend pieces and the git history for conventions:
Let me examine how folders are used in the frontend and check the remaining item-related components:
Now I have a clear picture. Let me check
MapPins.jsfor the existing folder-path convention and the icons available:I have everything I need. Let me start implementing — first the backend models:
Now the Foundry sync route — the folder tree mirroring and item filing:
Let me verify the Foundry Folder data model so the module filters world folders correctly:
Now the Foundry module — send the world's item folder tree and each world item's folder:
Now let me wire Foundry folder events so folder changes reach Dragonroll even when no item changed:
Let me refine the backend sync: the module always sends the complete tree, so the world owns it:
Now the item routes — expose the folders alongside items:
Let me wire the Foundry folder hooks into the module's event loop:
Now the frontend: a small pure service that groups items under their synced folders:
Let me rewrite that service cleanly:
Item folders must not leak into the note tree — filter the note/folder routes:
Now let me write the tests for this feature:
Implementation is ready for review: #46
The automated implementation stopped because of an internal error. Please check the worker logs for details.