Consider an alternative API surface which unifies all of the get/find/create options in to a single function which takes arguments expressing what to do in terms of intermediate and endpoint creation during path traversal. This could replace all of the get, get_path, etc. options plus any creation options.

We need ways to read and write the data attached to each node. Implement this.

Whether this is identical to renaming, or otherwise, I'm not entirely sure yet - needs a little think about the API surface, but broadly speaking, being able to move a thing somewhere else is needed!

As titled, need to be able to remove/remove_all.

At the moment, paths passed to functions are treated extremely naively (no support for root dirs, parent/child traversal, etc.)

This should be improved, and we probably want to pull some of that code outside of the directory methods themselves, especially as we're likely to want to include some default file system traversal functions too.

At the moment, we have no creation functions! Implement these, for both local and path scopes.

Crate documentation needs to be done, this is a tracking issue for that. Not going to invest time in that until the API is reasonably stable and complete and it's ready for a publish for a working version to crates.io. Also needs battle testing as part of internal projects first!

We need a consistent approach to naming for API calls, we have more available and more
contextual available than simply mirroring the std::fs API, which is really a thin layer
on a *nix-like file system.

Something like...

Info

count
count_dir
count_file

Retrieval

get
get_dir
get_file

get_path
get_path_dir
get_path_file

Creation