You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
I find that
docs/bar
anddocs/foo
do not appear as collection (no index?)Most surprising thing that happens is when I edit
docs/root
and change the path tobaz
. This disrupts then entire collection completelyWhat in the world happened here?
docs/baz
?docs/baz/baz/index.*.md
and not the expecteddocs/baz/root.*.md
decap-server
died withError: 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?
Beta Was this translation helpful? Give feedback.
All reactions