Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling folders in File API #146

Closed
m-mohr opened this issue Nov 2, 2018 · 1 comment
Closed

Handling folders in File API #146

m-mohr opened this issue Nov 2, 2018 · 1 comment
Milestone

Comments

@m-mohr
Copy link
Member

m-mohr commented Nov 2, 2018

The API specification doesn't explicitly specify whether it is possible to delete folders or just files. We may want to allow deleting folders. Also, other endpoints need to be more concrete how to handle folders. Putting folders may not be possible though. Issue may be obsolete with #135.

@m-mohr m-mohr added this to the v0.4 milestone Nov 2, 2018
@m-mohr
Copy link
Member Author

m-mohr commented Feb 6, 2019

Added the following descriptions for folder handling:

  • GET /files/{user_id}: Folders MUST NOT be listed separately so each element in the list MUST be a downloadable file.
  • GET /files/{user_id}/{path}: If a folder is specified as path a FileOperationUnsupported error MUST be sent as response.
  • DELETE /files/{user_id}/{path}: Resulting empty folders MUST be deleted automatically. Back-ends MAY support deleting folders including its files and subfolders. If not supported by the back-end a FileOperationUnsupported error MUST be sent as response.
  • PUT /files/{user_id}/{path}: Folders are created once required by a file upload. Empty folders can't be created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant