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>
15 lines
534 B
Python
15 lines
534 B
Python
"""The web face: the tabs, the JSON routes behind them, and the Jinja
|
|
environment. The queue brings its own routes and elements (`pipeline.web`),
|
|
auth the login page and `<auth-account>` (`auth`); `app.main` puts them
|
|
together. One door for all of it."""
|
|
|
|
from __future__ import annotations
|
|
|
|
from app.web.api import router as api_router
|
|
from app.web.pages import (
|
|
SETTINGS, STATIC_DIR, TABS, router as pages_router, templates,
|
|
)
|
|
|
|
__all__ = ["SETTINGS", "STATIC_DIR", "TABS", "api_router", "pages_router",
|
|
"templates"]
|