Closed goodmami closed 2 years ago
Actually I'm having second thoughts about this one. While it could be useful, I prefer simple solutions, and just raising a warning on any redirect is probably the easiest thing for now.
Or even easier: raise an exception instead of a warning, and don't bother with redirects at all. This has the benefit that messages could be displayed that are not about redirects.
As part of #142, I imagined a
warn
key on the tables of deprecated projects. This issue is for tracking that feature.I think I might prefer the more nouny
warning
instead ofwarn
. The warning should be issued before the test for the version, so if someone from the future tries to get a then-current version for an outdated identifier (such asewn:2025
instead ofoewn:2025
), they will see the warning about the ID change before the error message about the missing version.