Closed jimafisk closed 1 year ago
Currently if you add a path override in plenti.json, that name will become a folder and an invisible index.html file is put inside that folder which a browser will render like a regular path.
plenti.json
index.html
Currently I'm working on better 404 error handling (https://github.com/plentico/plenti/issues/264). With that, a typical route override could look like:
{ "routes": { "404": "/404" } }
This will produce a path like http://localhost:3000/404/index.html. However, for something like GitLab Pages custom error pages, they require a specific naming convention like http://localhost:3000/404.html. It would be nice if you could accomplish this as a route override:
{ "routes": { "404": "/404.html" } }
This is available in v0.6.2.
Currently if you add a path override in
plenti.json
, that name will become a folder and an invisibleindex.html
file is put inside that folder which a browser will render like a regular path.Currently I'm working on better 404 error handling (https://github.com/plentico/plenti/issues/264). With that, a typical route override could look like:
This will produce a path like http://localhost:3000/404/index.html. However, for something like GitLab Pages custom error pages, they require a specific naming convention like http://localhost:3000/404.html. It would be nice if you could accomplish this as a route override: