Skip to content

Path metadata does not support case sensitive paths #7461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mastercoms opened this issue Apr 19, 2025 · 0 comments
Open

Path metadata does not support case sensitive paths #7461

mastercoms opened this issue Apr 19, 2025 · 0 comments
Labels
type: bug code to address defects in shipped code

Comments

@mastercoms
Copy link

mastercoms commented Apr 19, 2025

Hi, the path metadata handler throws an invalid path error if there are any capital letters in the path.

validateMetaField calls getProcessSegment which calls prepareSlug, which calls toLocaleLowercase. Because prepareSlug produces a different, lowercase string, there's a mismatch and invalid path is thrown.

I think folder names should be allowed to be capitalized. We use folder names in nested collections cosmetically, such that we need capitalization in folder names.

Let me know if any more info from the template is needed.

@mastercoms mastercoms added the type: bug code to address defects in shipped code label Apr 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

1 participant