Using nested collections

[tpluscode]

Do I get it right, that nested collections only really work when all files are called index.* and their path serves as the collection.

I have this example structure, and a similar in a much bigger existing site I try to migrate to decap.

docs/
├── bar
│   ├── child
│   ├── bar.de.md
│   └── bar.en.md
├── foo
│   ├── child.de.md
│   └── child.en.md
├── foo.de.md
├── foo.en.md
├── root.de.md
└── root.en.md

I find that docs/bar and docs/foo do not appear as collection (no index?)

Most surprising thing that happens is when I edit docs/root and change the path to baz. This disrupts then entire collection completely

docs/
├── bar
├── baz
│   ├── bar
│   │   ├── bar.de.md
│   │   └── bar.en.md
│   ├── baz
│   │   ├── index.de.md
│   │   └── index.en.md
│   ├── foo
│   │   ├── child.de.md
│   │   └── child.en.md
│   ├── foo.de.md
│   └── foo.en.md
└── foo

What in the world happened here?

1. Everything moved to docs/baz?
2. The file I edited actually became docs/baz/baz/index.*.md and not the expected docs/baz/root.*.md
3. And decap-server died with Error: ENOENT: no such file or directory, rename '/path/docs/bar/bar.en.md' -> '/path/docs/baz/bar/bar.en.md'

Wouldn't this entire feature be some much easier if it just worked like a regular editor with directories and files?

[pranaysahith]

Wouldn't this entire feature be some much easier if it just worked like a regular editor with directories and files?

Totally agree with this. The whole nested collections is unusable because of how it is designed and folders linked to the index file.

@martinjagodic @demshy Can we please discuss the possibility of having a configuration option to make nested collection work just like normal directories and files?

(I am happy to raise PRs)

[martinjagodic]

I am very open to a PR on this topic. I agree that a dir-file editor would be the most intuitive option. But it has to be backward-compatible and support index files. This PR will add a feature to differentiate index files from others: #7382, so please consider it when starting your PR.

[martinjagodic]

The index_file feature is not directly related to nested collections. It adds a way for the index file to have a different set of fields and is distinguished with a home icon on the collection view. I mentioned it because it modifies some code related to nested collections.

[pranaysahith]

I see, can you please take a look the PR #7681 and let me know if it can be merged separately?

[pranaysahith]

@martinjagodic Did you get a chance to review the PR #7681 ? Any feedback is highly appreciated.

[martinjagodic]

Not yet, I'm quite busy this week. Your PR is quite large, so I need a sizable chunk of free time to review it.

[pranaysahith]

Hi @martinjagodic, hope you had a nice break over the holidays.
A gentle reminder to review the PR #7681
Thank you!