-
-
Notifications
You must be signed in to change notification settings - Fork 813
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
VFS Capability detection, other extensions #804
Comments
As discussed, @mahsashadi will do some work related to this in the following stages:
Massive thanks! |
Also, @ajmeese7 wanted to have a look at archive extensions. Thanks a bunch! |
I continue with capability detection of VFS: These changes are considered added method has some argument. If you still have the idea of capability caching, maybe we should create another PR that changes the api to support methods without arguments. |
@mahsashadi Yeah, let's tackle the caching in a separate PR. It needs further discussion. I have some ideas about this already, but let's take it when the time is right. |
I continue with adding total values to VFS stat api (needed for pagination in file manager): I also make another pull request for capability-caching: |
I made another PR for VFS context-aware sorting in client-side. |
VFS could benefit from capability detection so that clients is aware of what a filesystem source is capable of.
This would allow for adding extensions on the client that are context aware, like pagination and archives.
Split out from discussions in:
Work done on this:
Pending:
Relevant:
The text was updated successfully, but these errors were encountered: