feat(soccer-app): add accessible team insights panel - #31
Conversation
added 2 commits
August 10, 2026 17:13
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Task-Id: 01KZPAGGGCGHXD9PG5YXC39FQQ Prompt-Version: 1c9c10e027a2
…6D/shared-orchestration-context-the-parent-epic-sever' into bgagent/01KZPAGGGCGHXD9PG5YXC39FQQ/shared-orchestration-context-the-parent-epic-sever
Owner
Author
|
chore(restack): re-merged updated predecessor branch into this PR. Absorbed: The predecessor branch ( Conflicts: None — the merge was clean. My Team insights panel README section and the predecessor's Shared team metrics section coexist without overlap; Build/test:
No scope changes — maintenance re-stack only. |
Owner
Author
Background agent — COMPLETED
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a compact, accessible Team Insights panel to the team detail view (TG-12). The panel builds on the shared team metric helpers and the refactored views introduced earlier in this chain.
TeamInsightscomponent surfaces three shared metrics for the selected team:performanceLabel.goalDifference,winRate, andperformanceLabelfromsrc/utils/teamMetrics.ts(no recomputation).TeamDetail's body, above the existing statistics section.Accessibility
<section>labelled by an<h3>heading (aria-labelledby) and a<dl>/<dt>/<dd>description list for metric name/value pairs.Visual design & responsiveness
auto-fitand collapses to a single column at the existing 768px breakpoint, remaining usable on narrow screens.Docs
soccer-app/README.mdwith a short feature note describing the panel.Issue
TG-12: Add accessible team insights panel (epic: ABCA Jira stacked corrections acceptance round 2).
Build & test results
Run in
soccer-app/(dependencies installed withnpm installfirst, as they were not present):npm run build→ pass (tsc -b && vite build, built in ~114ms, 22 modules transformed).npm run lint→ pass (oxlint, exit code 0, no warnings).The repo has no automated test suite; verification was via the TypeScript build and linter.
Decisions made
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.
Agent notes
teamMetrics.tshelpers (added earlier in the chain) made this straightforward — the panel is a thin, presentational layer over existing, deterministic metric functions. Build and lint passed first try.soccer-app/node_moduleswas not pre-installed for the nested app, somise run build/npm run buildinitially failed withtsc: not found. Runningnpm installinsoccer-app/resolved it.soccer-app/;misetasks (build,lint,dev) proxy tonpmscripts in that dir. Components live insrc/components, shared logic insrc/utils, styles centralised insrc/App.csswith sectioned comment banners. Commit messages follow conventional-commit style with a module scope (e.g.feat(soccer-app): ...).npm cistep or documenting thenpm installrequirement so nested-app builds work out of the box. Since there are no tests, a lightweight component test setup (e.g. Vitest + Testing Library) would help guard accessibility/behavior regressions.🤖 Generated with Claude Code