Remove the MOVED redirects
MOVED and _moved answered 301 for twelve paths the settings cog moved off of a few days ago. A browser caches a 301 indefinitely, so a path reused later would be unreachable through no fault of that page, and a one-person app has no outstanding bookmark to protect. Drop the table, the routes, its export from app.web, and the tests that pinned it; the old paths now answer plain 404. Keep the test that every section of the Sources page exists, rewritten without MOVED. Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
This commit is contained in:
1 parent
706b127bc0
commit
92ff2bc069
5 files changed
+24
-78
No files matched your search
@@ -208,8 +208,8 @@
|
||||
|
||||
// Sources shows one section: the one the fragment names or contains, or the
|
||||
// first when there is none or it names none, so `/settings/sources#runs` (a
|
||||
// rail link, an old path's 301, the Search agents page's "follow it under
|
||||
// Runs") opens Runs, and so does `#messages`, the log at its end. The rest
|
||||
// rail link, or the Search agents page's "follow it under Runs") opens
|
||||
// Runs, and so does `#messages`, the log at its end. The rest
|
||||
// are hidden, not removed, so their scripts still find their roots. It runs
|
||||
// as the script loads rather than on DOMContentLoaded, so the page never
|
||||
// paints all three first.
|
||||
|
||||
Reference in new issue
Block a user