settings.base_url still used in 7 locations after frontend_url migration #215
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
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/basketball-api#215
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?
Type
Feature
Lineage
Standalone — discovered during validation of
forgejo_admin/basketball-api#201(review-514-2026-03-28).Repo
forgejo_admin/basketball-apiUser Story
As a developer maintaining basketball-api
I want all references to
settings.base_urlmigrated tosettings.frontend_urlSo that the codebase is consistent after the rename in PR #196 and no compatibility shims are needed.
Context
PR #196 renamed
settings.base_urltosettings.frontend_urlin the config model. PR #203 fixed the test regression this caused, restoring the pipeline to green (614 passed). However, the validation review found that 7 non-test locations still referencesettings.base_url(orbase_urlfrom settings). These likely work via a compatibility alias or property, creating confusion and technical debt.File Targets
Files the agent should modify:
settings.base_urlor importingbase_urlfrom settings — replace withsettings.frontend_url/frontend_urlbase_urlcompatibility alias/property if presentFiles the agent should NOT touch:
Acceptance Criteria
settings.base_urlreferences replaced withsettings.frontend_urlbase_urlremoved from the settings modelTest Expectations
pytest tests/ -x -qConstraints
grep -r "base_url" src/that zero references remain after cleanupChecklist
Related
westside-basketball— project this affectsforgejo_admin/basketball-api#196— original rename PRforgejo_admin/basketball-api#203— test fix PRforgejo_admin/basketball-api#201— validation issue (now closed)