-
Notifications
You must be signed in to change notification settings - Fork 319
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
feat: Introduce remote scheme #1152
base: main
Are you sure you want to change the base?
Conversation
cc @sxyazi, I'm not sure if this PR is the right size for merging. Could you first review the overall design? |
Thanks for the PR! I think we should create a new crate As for the scheme configuration, I don't think it's reasonable to keep it in |
Typically, I expect a complete feature to be merged. Perhaps we can create a separate branch for ongoing work, or you could just give me write access to your fork so I can participate in the development? |
Yes, I have enabled
Nice idea, I will do this. |
DONE, please take a look.
I tried but failed. |
Thanks, the config for remote services should be lazily initialized on use – I'll refactor it.
Why does
Yeah currently Yazi's filesystem isn't abstracted and is full of local fs API calls. I think the first step should be to abstract the common APIs into the |
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
6c0a482
to
f5598eb
Compare
4eec20b
to
ed6ae00
Compare
71690f8
to
33d04f9
Compare
8f9390b
to
f865910
Compare
This PR intends to introduce the new remote scheme concept in yazi. After this new feature introduced, users can use yazi to visit and manage files store in remote storage services like s3, gcs, webdav, dropbox and so on.
This PR just a start of this PR and not integrate with file operations yet.