You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The file manager currently doesn't trigger any events to notify other parts of the system about added/moved/removed etc files. The only way for e.g. plugins to get notified about added/uploaded files is listening to the Upload event, which only is triggered for actual file uploads, not for files added through other means, e.g. the watched folder.
We should have the file manager generate its own set of events for plugins such as the AutoSelect Plugin to hook into.
A first attempt at a list:
FileAdded
FileRemoved
FolderAdded
FolderRemoved
All those events would have a payload structured somewhat like this:
location: The identifier of the storage location of the affected file/folder
path: The path within the storage location to the affected file/folder
name: The name of the affected file/folder
For the SD card stuff we either need to have those events triggered in the comm layer for now, or don't trigger them at all, until that stuff is migrated to a proper StorageInterface implementation.
@Salandora do we also need events for copy/move or should it be sufficient to replicate those as *Added for a copy and *Removed + *Added for a move?
The text was updated successfully, but these errors were encountered:
The file manager currently doesn't trigger any events to notify other parts of the system about added/moved/removed etc files. The only way for e.g. plugins to get notified about added/uploaded files is listening to the Upload event, which only is triggered for actual file uploads, not for files added through other means, e.g. the watched folder.
We should have the file manager generate its own set of events for plugins such as the AutoSelect Plugin to hook into.
A first attempt at a list:
All those events would have a payload structured somewhat like this:
location
: The identifier of the storage location of the affected file/folderpath
: The path within the storage location to the affected file/foldername
: The name of the affected file/folderFor the SD card stuff we either need to have those events triggered in the comm layer for now, or don't trigger them at all, until that stuff is migrated to a proper
StorageInterface
implementation.@Salandora do we also need events for copy/move or should it be sufficient to replicate those as
*Added
for a copy and*Removed
+*Added
for a move?The text was updated successfully, but these errors were encountered: