Tools ideas
add_path_get and path.KeyPath are useful to get a "flat read access" from nested stores, but it's just for getting data: It's not enough to get a full KvReader (needs iter, len, contains) or KvPersister (needs del and set). kv_walk is relevant there. One could imagine a dol.trans.store_decorator that takes the same arguments as kv_walk (or a "kv_walker" object), and decorates the store in such a way as to offer a store whose keys are the paths of the kv_walk.
Related to the "flat stores" is this issue on hypercubic keys and issue on subscripting abilities.
dol.filesys deals with file/folder traversal with max_levels and isdir/isfile only, and these are somewhat baked in the code. One could envision a future for dol.filesys that would offer the same functionality, but also more, expanding the tree traversal aspects to anything involving path, key and value.
Other
Can see applications of remap for inspiration of applications.
┆Issue is synchronized with this Asana task by Unito
Tools ideas
add_path_getandpath.KeyPathare useful to get a "flat read access" from nested stores, but it's just for getting data: It's not enough to get a fullKvReader(needs iter, len, contains) orKvPersister(needs del and set).kv_walkis relevant there. One could imagine adol.trans.store_decoratorthat takes the same arguments askv_walk(or a "kv_walker" object), and decorates the store in such a way as to offer a store whose keys are the paths of the kv_walk.Related to the "flat stores" is this issue on hypercubic keys and issue on subscripting abilities.
dol.filesysdeals with file/folder traversal withmax_levelsandisdir/isfileonly, and these are somewhat baked in the code. One could envision a future fordol.filesysthat would offer the same functionality, but also more, expanding the tree traversal aspects to anything involving path, key and value.Other
Can see applications of remap for inspiration of applications.
┆Issue is synchronized with this Asana task by Unito