refactor: rename the "provider" term in VFS config to "service" #3403
+110
−125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #3396
This PR corrects terminology in the virtual filesystem before the official release by introducing a new "service" concept to distinguish it from the existing "provider":
host,port,user, etc.If you used the
providersfield invfs.toml, please replace it withservices. For example:The latest nightly documentation has been updated to reflect this change: https://yazi-rs.github.io/docs/next/configuration/vfs