school_compare

4 Commits

Author	SHA1	Message	Date
TudorandClaude Opus 4.8	368b9f2b59	fix(admissions): render trend with Chart.js instead of scaled SVG The hand-rolled SVG sparkline used px font sizes inside a 520-wide viewBox that stretched to the full card width, so labels ballooned ~4x and collided — and with 10+ years of real data the per-point labels and year ticks overlapped badly, while the oversized chart stretched the "this year" view. Replace it with a Chart.js line chart (AdmissionsTrendChart) in a fixed 200px wrapper, matching PerformanceChart: responsive px fonts, auto-skipping x ticks, auto-scaled y-axis clamped to 0-100, emphasised latest point. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-19 18:59:57 +01:00
TudorandClaude Opus 4.8	4de7e559e9	feat(admissions): surface multi-year admissions trend on school detail Build and Push Docker Images / Build Backend (FastAPI) (pull_request) Successful in 22s Details Build and Push Docker Images / Build Frontend (Next.js) (pull_request) Successful in 53s Details Build and Push Docker Images / Build Pipeline (Meltano + dbt + Airflow) (pull_request) Successful in 11s Details Build and Push Docker Images / Trigger Portainer Update (pull_request) Has been skipped Details The school detail page only showed the latest admissions year. We store every year, which is more decision-relevant for parents (the trend and its consistency matter more than a single noisy year). Backend now returns the full admissions_history (oldest first) alongside the existing latest-year object. The primary SchoolDetailView gains a header toggle ("This year \| N-year trend") that swaps the Q&A for an SVG sparkline of the first-choice offer rate. The toggle only appears when >=2 years carry an offer rate; otherwise it falls back to the single-year card. Both views share one CSS-grid cell so switching causes no layout shift. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-19 18:41:03 +01:00
Tudor	e7c26a83db	Updating homepage last update date Build and Push Docker Images / Build Backend (FastAPI) (push) Successful in 14s Details Build and Push Docker Images / Build Frontend (Next.js) (push) Successful in 52s Details Build and Push Docker Images / Build Pipeline (Meltano + dbt + Airflow) (push) Successful in 17s Details Build and Push Docker Images / Trigger Portainer Update (push) Successful in 1s Details	2026-06-18 14:20:17 +01:00
TudorandClaude Opus 4.8	3785f0c977	fix(pipeline): invoke dbt via python module to avoid Fusion shadowing Build and Push Docker Images / Build Backend (FastAPI) (push) Successful in 53s Details Build and Push Docker Images / Build Frontend (Next.js) (push) Successful in 56s Details Build and Push Docker Images / Build Pipeline (Meltano + dbt + Airflow) (push) Successful in 2m0s Details Build and Push Docker Images / Trigger Portainer Update (push) Successful in 1s Details The standalone dbt Fusion binary (dbt-core 2.x) on PATH shadows the pip-installed classic dbt-postgres ~=1.10 and rejects the Postgres adapter (dbt1005), breaking every DAG's dbt_build task. Invoke dbt via `python -m dbt.cli.main` in the DAGs and the Dockerfile dbt deps step so the classic Postgres-capable engine is always used regardless of PATH. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-18 13:41:35 +01:00