Remove dead auth code + stale references after Jinja2 removal #152
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-api#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Lineage
plan-pal-e-docs→ Phase 4 → Phase 4d (post-sunset cleanup)Repo
forgejo_admin/pal-e-docsUser Story
As a maintainer
I want dead code removed after the Jinja2 sunset
So that the codebase is clean and doesn't confuse future contributors
Context
QA review of PR #151 (Jinja2 removal) identified 3 non-blocking nits — dead code that was only used by the now-deleted frontend.
File Targets
src/pal_e_docs/blocks/compiler.py— remove stale docstring referencing deleted sanitize/autolink/wrap_tables modulessrc/pal_e_docs/auth.py— remove dead functions:verify_password,authenticate_user,get_current_user(no longer called after SessionMiddleware removal)src/pal_e_docs/config.py— remove orphansecret_keyfield (was only used by SessionMiddleware)Files NOT to touch:
src/pal_e_docs/routes/— API routes, don't changesrc/pal_e_docs/models.py— don't changesrc/pal_e_docs/blocks/parser.py— don't changeAcceptance Criteria
auth.pysecret_keyremoved from configTest Expectations
pytest tests/ -vConstraints
Checklist
Closes #152
Related
pal-e-docs— project