BlobTree API refactor including newfile() / newdir(), and renaming. #45
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 PR updates and refines the
BlobTree
API and renamesBlobTree
->FileTree
andBlob
->File
as mentioned to fix #41. In the rename, the previous nameBlobTree
is still allowed for now, though both the binding and use in Data.toml are deprecated.It also significantly updates and refines the mutation API — the
newfile()
andnewdir()
functions so that they're primarily in-place APIs. The older out-of-placenewfile()
andnewdir()
have been deprecated. (Before this refactor the API looked slightly nicer, but was inherently less efficient than the native file APIs.)In addition, add a few missing pieces of query functionality
/
-separated path strings in anyFileTree
accessors for convenience. (Previously these would raise an error.)delete!(tree, path)
. Requires the tree's root object to implementdelete!(root, path)
rm(tree)
.TODO
newfile()
andnewdir()
.