What to do with importing nested directory structures?

[sumnerevans]

How should we handle importing a directory that is structured something like this:

my-directory
|-> foo/
|   |-> bar.yaml
|   |-> cool-vid.mp4
|   '-> other-vid.mkv
|-> bar/
|   |-> baz/
|   |   |-> omega.yaml
|   |   |-> pi.mp4
|   |   '-> tau.mp4
|   |-> alpha.yaml
|   |-> beta.yaml
|   '-> gamma.mp4
|-> delta.mp4
'-> epsilon.mp4e

Note this needs to handle both PathSource and IPFSSource as well as any other source that allows importing of directories.

[robozman]

Could we treat each subdirectory the same way we treat imports in a sources.yaml?

[sumnerevans]

What do you mean? Creating an implicit import for each folder and namespacing accordingly? In this scenario, we would have the following namespaces:

• my-directory:foo
• my-directory:bar
• my-directory:bar:baz

[sumnerevans]

Discussed this with @robozman . The directory structure that I described would be create the following namespaces:

• my-directory
• my-directory:foo
• my-directory:bar
• my-directory:bar:baz

Each of these namespaces will be populated with the corresponding assets. A couple of examples include:

• my-directory:delta.mp4
• my-directory:bar:baz:tau.mp4