I noticed that there isn’t a way to browse snapshots using the API, would be nice if that information is being exposed via the API as well.
Also exposing the notifications would be greatly appreciated. It’s now only possible to get the amount of new notifications (undocumented), but I didn’t encounter a way to retrieve the actual notifications themselves.
the get events method returns the events but sometimes a description is missing (undefined).
For now I encountered it with the etypes: repo-create and repo-delete
PERMISSION FAULT: Error in getting File History information:
When a user tries to get the file history of a file which is read-only the API returns forbidden, although in Seahub the same information can be accessed perfectly fine.
This should be fixed so a user that has read-only access to a file can still read the file history via the API as intended
This one is annoying: when trying to open a file using OWA, it always returns {"error_msg":"path invalid."}
As soon as I use an incorrect filepath it says: {"error_msg":"File /subfolder/DOESNTEXIST.docx not found."}
The path I provide is 100% correct, there are no entries in any of the logs about this failed API call and yet I never get the response I’m looking for…
The recursive dir structure seafile returns is very impractical.
You’d expect some kind of recursive array as in
Library Name
___subfolder
______another subfolder
______subsubfolder
___subfolder
Instead, it just returns a flat list as such:
Library Name
subfolder
another subfolder
subsubfolder
subfolder
with a parent field. It’s really impractical to loop over a flat list and make a tree out of it in HTML
List Directory Entries
GET https://cloud.seafile.com/api2/repos/{repo-id}/dir/
t (optional): If set t argument as f, will only return file entries, and d for only dir entries.
recursive (optional): If set t argument as d AND recursive argument as 1, return all dir entries recursively