Issue: Uppercase/lowercase of content filenames.

Describe the bug (Part 1)

Maybe more a feature request than a bug?

• Open dashboard.
• Create new content file via button Create content.
• Enter a title FormControlGroup.
• The created file is: formcontrolgroup.md (lowercase).
• Because we use camel-case naming in some HUGO projects for delibarate reasons (before-rendering processing):
• • Close editing view of file formcontrolgroup.md.
• • Close dashboard. (Because I couldn’t find a refresh button or so and thought it could be the trick).
• • Rename file in VSCode explorer to formControlGroup.md (camel-case).
• Open FM dashboard and click entry with title FormControlGroup for editing.
• Save file.
• The file is opened and saved as formcontrolgroup.md (lowercase).

Expected behavior (Part 1) The file is opened and saved as formControlGroup.md (camel-case).

Describe the bug (Part 2) I don’t know if it’s related.

• Close all FM views. Open VSCode explorer.
• Open the file formControlGroup.md (camel-case) by double-click.
• Click FM-Button in left sidebar.
• See the three loading dots for several minutes. Even after 1/2h nothing has happened.
• (Addendum: Opening the FM dashboard in parallel seems to speed up the process.)

Expected behavior (Part 2)

• FM edit panel opens for the opened file formControlGroup.md (camel-case).

Desktop (please complete the following information):

• OS: Win10
• Current VScode version.
• Because we thought the reason for endless waiting could be “Git talks by VSCode” we’ve disabled it but no change.

Additional context We have to close and reopen VSCode before FM accepts the camel-case file, but then we have to wait before FM has scanned all files in dashboard which goes really slow for just 15 files in just one configured frontMatter.content.pageFolders. Just for the record: It’s not only FM that is annoying slow immediately after VSCode initialisation.

Maybe a refresh button or something like that in dashboard would be nice.

Or highest happiness: Possibility to save or rename files camel-cased so that FM is aware of it without the need to rescan everything.

Thank you!

[ReLater]

But then scanning is extremly slow in our environment. But it’s no problem for me to use smaller VSCode-workspaces in the future to speed the thing up.

[estruyf]

A new setting frontMatter.file.preserveCasing is available to do exactly what it says. It preserves the casing on file creation based on the title you enter during the creation process.