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
Since every modern browser, Javascript runtime and filesytem supports unicode in their URIs/filenames I think it's fair to accept this is as a correct path
We could add an option to try to substitute certain characters using a function like (https://github.com/sindresorhus/transliterate) but it still would not support languages with another script such as Chinese or Japanese
In this case we should find a solution for finding the matching route when retreiving it through the cms.maybeGet function. Because it's resulting a notfound:
const data = await cms.maybeGet(MySchema({path: slug}))
This snippet is resulting in a notfound when the slug contains č.
To fix this we can decode the received slug:
const data = await cms.maybeGet(MySchema({path: decodeURI(slug)}))
When entering a page title like
Vančura
, the path is not slugged correct:vančura
.I should expect that
č
would be transformed intoc
.The text was updated successfully, but these errors were encountered: