Allow the use of relative paths in open_matrix_dir/open_fragments_dir

[bjmt]

Hi,

Thanks again for the great package. I was wondering what you thought of adding the option to functions such as open_matrix_dir() and open_fragments_dir() to avoid the use of the normalizePath() function internally, which expands relative paths. This can be annoying when I'm working with a BPCells-backed Seurat object on different computers, since encoded within the Seurat object will be the whole absolute path to where the matrix/fragment/whatever directory was first opened. (Unless the next computer opening the object has the exact same path structure, it will then break.) Having the option to keep relative paths (for example if I create a project directory, and only ever work within this directory and keep all paths relative to it) would make sharing/transferring Seurat & BPCells folders a bit easier.

What do you think? For now I'm manually resetting the path within the BPCells objects inside the Seurat object whenever I encounter this situation, but I think it would simpler to just give users more control over the folder paths.

Thanks!

[immanuelazn]

Hi @bjmt Think this is pretty possible, Ill see what I can do! No timeline for when I can get on this just yet.

Immanuel