Clean up QA nits from dual-auth and jersey profile PRs #260
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
ldraney/basketball-api#260
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
Discovered scope from QA reviews of PR #258 and PR #259 (2026-03-30).
Repo
forgejo_admin/basketball-apiUser Story
As a developer
I want auth and profile code to follow consistent type annotation patterns
So that the codebase stays clean and self-documenting
Context
QA reviews of PR #258 (dual-auth) and PR #259 (jersey profile fields) flagged three non-blocking nits that were approved but deferred.
File Targets
Files the agent should modify:
src/basketball_api/auth.py-- (1) Add return type annotation toget_parent_dual_auth, (2) Remove redundantaliason token query param if Query default already matchessrc/basketball_api/routes/players.py-- (3) Changejersey_order_status: str | Nonetostrin PlayerProfileResponse since the model server default guarantees non-nullFiles the agent should NOT touch:
Acceptance Criteria
get_parent_dual_authhas a return type annotationjersey_order_statusis typed asstr(non-optional) in PlayerProfileResponseTest Expectations
pytest tests/ -x -qConstraints
Checklist
Related
project-westside-basketball