Version 6.3.0
Application Changes
-
Add fuzzy matching for panelist slugs in the
panelists.details
route. The fuzzy matching slugifies the inputpanelist_slug
value and compares it against the list of all panelist slugs.If the slugified value matches a valid panelist slug and the slugified value does not match the original
panelist_slug
value, then redirect the user to the correct path for the panelist. If there isn't a match, then redirect the user topanelists.index
.The extra check between the slugified
panelist_slug
value against the request'spanelist_slug
is to prevent the chance of an infinite redirect loop from happening.For example, if the user requests
/panelists/Luke%20Burbank
will match the slugified value ofLuke%20Burbank
toluke-burbank
and redirects the user to/panelists/luke-burbank
. However, if the user requests/panelists/Luke%20Burbonk
, there won't be a match and redirects the user to/panelists
. -
Similar updates to the corresponding guests, hosts and scorekeepers routes have also been made.
-
Add testing for the new slug fuzzy matching redirects for guests, hosts, panelists and scorekeepers.
Component Updates
- Upgrade Flask from 3.0.3 to 3.1.0
- Upgrade Markdown from 3.5.2 to 3.7.0
Development Changes
- Added test for
errors.not_found
Pull Request(s): #98
Full Changelog: v6.2.5...v6.3.0