Type of Change
Coming out of #1116 , one thing that will be useful to have a configuration option for is the trailing forward slash in a URL, e.g.
http://www.example.com/about
http://www.example.com/about/
Different web hosts / servers threat this differently, and not sure if there is also a "canonical" way of instrumenting this, or if it's mostly just for convenience / vanity?
Currently Greenwood assumes / sets a trailing forward slash automatically.
Summary
So the need here would be to enable a configuration option, e.g.
// greenwood.config.js
export default {
trailingForwardSlash: true|false // default is true
}
At the very least it should be supported in all instances basePath were supported in
- The graph
- Pages (static and SSR routing)
- API Routes
- Adapters (splat, dynamic routing, etc)
- GraphQL / Content as data
This post may be worth reading - https://bjornlu.com/blog/trailing-slash-for-frameworks
Type of Change
Coming out of #1116 , one thing that will be useful to have a configuration option for is the trailing forward slash in a URL, e.g.
http://www.example.com/abouthttp://www.example.com/about/Different web hosts / servers threat this differently, and not sure if there is also a "canonical" way of instrumenting this, or if it's mostly just for convenience / vanity?
Currently Greenwood assumes / sets a trailing forward slash automatically.
Summary
So the need here would be to enable a configuration option, e.g.
At the very least it should be supported in all instances
basePathwere supported in