Flattened path is not correctly handled for folders

[zce]

Flattened path is not correctly handled for folders

[zce]

The design of the s.path() schema is to omit the 'index' automatically.

The main scenario I consider is that many times we will choose to put the assets related to a document in the same directory, and then name the document index.md. At this time, index.md is generally meaningless.

 ├── content
 │   ├── posts
 │   │   └── hello-world
 │   │       ├── cover.jpg
 │   │       └── index.md

I know what you're saying, but I don't know in what scenario the directory and file basename will be the same.

If there is indeed such a scenario, adding an option parameter would be a better choice.

[marcocondrache]

I get what you're saying. For my setup, I'm putting together a sidebar that uses the path property to figure out which post is currently selected. The issue crops up when I'm dealing with both architecture.md and a folder (with an index) – they end up with the same path, making it tricky to tell them apart. Your thoughts make sense, and while it might be a bit of a specific case, it's still possible. So, if you're cool with it, having an option for users to pick what works best for them would be great.

I forgot to evidence that a folder is represented as a submenu in the sidebar. So, to group all the posts together under one main category, I need to figure out if they're hanging out in a folder along the path. But when I've got two files with "product/architecture" (doing the folder thing), it gets tricky to tell if it's a folder (and a submenu) or not.

[zce]

If you agree with me, please feel free to modify your PR and design a removeIndex option for s.path()?

[marcocondrache]

If you agree with me, please feel free to modify your PR and design a removeIndex option for s.path()?

Yup, that would be perfect! I've modified the PR with the options to remove the index. Thank you!