We now have a centralized pulse data directory.
It's handy to avoid manual corruption of the data files.
It's also handy to list the sandbox data without relying on a directory listing, where user could create directory manually.
It allows a simple management to diff works and send them, process doesn't need to avoid the data file.
BUT...
It's still possible to move, rename, or delete a resource folder, leading to a corrupted (unsync) data. Locking directory structure seems complicated to manage depending on the OS.
This risk is higher than editing or removing a hidden data file in a work folder
Relying only on one data source (the directory structure) avoid sync issue.
To validate a directory as a resource, we could test the json data file.
We now have a centralized pulse data directory.
It's handy to avoid manual corruption of the data files.
It's also handy to list the sandbox data without relying on a directory listing, where user could create directory manually.
It allows a simple management to diff works and send them, process doesn't need to avoid the data file.
BUT...
It's still possible to move, rename, or delete a resource folder, leading to a corrupted (unsync) data. Locking directory structure seems complicated to manage depending on the OS.
This risk is higher than editing or removing a hidden data file in a work folder
Relying only on one data source (the directory structure) avoid sync issue.
To validate a directory as a resource, we could test the json data file.