Currently, "folder path" is passed to check for allowed. We have all paths, and return only allowed. But maybe we should make it on demand. User wants to see subfolders of /my_files_1. We get from db only those. when user clicks again, we return next subfolder. This would be time consuming for UI currently (disappear on page change, have to track changes, cache invalidation...).
Edit: Currently folder path is not used. I added it simply for future proofing. So whole paradigm should be defined.
I want it to be like s3 paths, can be used for searching, but does not have any real value, only as tool for organizing.
Then sql's LIKE filter can be used to get certain subfolders
Currently, "folder path" is passed to check for allowed. We have all paths, and return only allowed. But maybe we should make it on demand. User wants to see subfolders of /my_files_1. We get from db only those. when user clicks again, we return next subfolder. This would be time consuming for UI currently (disappear on page change, have to track changes, cache invalidation...). Edit: Currently folder path is not used. I added it simply for future proofing. So whole paradigm should be defined. I want it to be like s3 paths, can be used for searching, but does not have any real value, only as tool for organizing. Then sql's
LIKEfilter can be used to get certain subfolders