Enhancement: Customizable file system oterator implementation #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jon Doron <jond@wiz.io>
Signed-off-by: Jon Doron <jond@wiz.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch introduces the capability to implement custom iterators for file system traversal. This flexibility is particularly beneficial for applications requiring specialized handling of file systems, such as iterating over archive formats (e.g., tar, zip) or employing alternative traversal logic. For instance, this feature addresses community requests for functionality to avoid following symbolic links during file system operations.
With this update, developers can tailor file system iteration to better meet their specific application needs.