[v5] Consider not converting all URLs to have a trailing slash
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 34
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 12
Description
I think this was carried from LNT v4, but there's no reason (AFAICT) to canonicalize all routes to have a trailing slash.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the v5 URL and routing entry points for the logic that adds trailing slashes. Reproduce the current canonicalization behavior across routes and identify which routes should retain their existing form. Done means v5 no longer canonicalizes every URL to a trailing slash, with behavior checks for the changed routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100