chore: add keyed fields in auth_test.go

[NigelByrne1]

• local linter wants named fields
• add Code: and Body: to TestAuthHandlerServiceAccount

[qodo-app-for-konflux-ci]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can copy the agent prompt from any finding and feed it to your IDE agent

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-app-for-konflux-ci]

PR Summary by Qodo

Use keyed response literals in authentication tests

🧪 Tests 🕐 Less than 5 minutes

AI Description

• Names mock response fields in service-account authentication test fixtures.
• Satisfies composite-literal linting without changing test behavior.

High-Level Assessment

The keyed literal approach is optimal because it satisfies linting, improves resilience to struct field reordering, and preserves existing test behavior.

Files changed (1) +4 / -4

Tests (1) +4 / -4

auth_test.goUse keyed fields in authentication response fixtures +4/-4

Use keyed fields in authentication response fixtures

• Adds explicit 'Code' and 'Body' field names to mock OpenShift responses in service-account authentication tests. Test inputs and expected behavior remain unchanged.

pkg/handlers/auth_test.go

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:10 PM UTC · Completed 4:19 PM UTC

Commit: 9ee3c25 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.87

[dirgim]

LGTM

[fullsend-ai-review]

Risk Assessment: low (1/5)

Details

Single test-only file change adding named struct fields to satisfy linter requirements, with minimal churn, one author, no protected paths, no dependencies, and no linked issue — composite score 0.62×1.125 + 0.38×1.43 ≈ 1.24, rounded to 1.

[fullsend-ai-review]

Looks good to me

[jencull]

lgtm