Repository navigation
docs: roadmap cleanup + chart-coordinate lifecycle readability pass - #296
Merged
pacharanero merged 2 commits intoSep 24, 2026
Merged
Conversation
…dinate lifecycle doc R1 (nullable chart-y) and R3 (APIM openapi sync) are both fully done - moved to Completed findings with evidence (PR #290; PR #281/#284/#291, #229 closed). R12 (Fenton removal): rcpchgrowth PR #126 / v4.6.5 stopped shipping the unlicensed LMS PDF. Noted as partial progress - the reference constants, loader, and CDC dispatch/chart branches are still present in rcpchgrowth source and untouched downstream, so the item stays open. Reworked spec/chart-coordinate-lifecycle.md for readability: dense paragraphs split into scannable bullet lists, bold lead-ins on key points, historical-comparison section restructured as a numbered procedure. No content added or removed.
…ponent CI step Two concrete steers from discussion, replacing the earlier disk-cache proposal: - Server: generate the full coordinate set once per process, in memory only. No disk persistence - no measurable benefit, and it risks a process silently serving coordinates from a stale engine version. This also removes most of the disk-cache coordination complexity (staging dirs, atomic publish, partial-write races, shared-volume writability) since nothing is shared or persisted. - React: leading proposal is a CI build step in the Component repo that regenerates the bundle from a pinned rcpchgrowth release, rather than hand-maintained/manually-regenerated data. Left open: whether the generated .ts modules stay tracked in Git or become a release-only artifact, and how the rcpchgrowth pin gets bumped. Updated the startup lifecycle, repository layout, testing strategy, benchmark plan, sequence, and open questions sections to match. Rewords roadmap R11 to summarise the same direction. Still a discussion draft - no runtime implementation.
pacharanero
deleted the
docs/roadmap-cleanup-and-chart-coordinate-lifecycle
branch
September 24, 2026 17:21
|
Seen on LIVE (merged by @pacharanero 3 minutes and 15 seconds ago) Please check your changes! |
|
@pacharanero @mbarton: the live deployment and APIM OpenAPI import completed successfully. Please verify the API operations and policies in the Azure portal. Deployment: https://github.com/rcpch/digital-growth-charts-server/actions/runs/36033787160 |
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.
What
y) and R3 (APIM OpenAPI sync) to Completed findings - both are done, with evidence.rcpchgrowthPR Large error for preterm babies plotted at 2 y and 1y #126 / v4.6.5 stopped shipping the unlicensed LMS PDF, but the reference constants/loader/dispatch code and all downstream repos are untouched. Item stays open.spec/chart-coordinate-lifecycle.mdfor readability only - dense paragraphs split into bullet lists, bold lead-ins, historical-comparison section restructured as a numbered procedure. No content added or removed.Why
R1 and R3 were sitting under active sections despite being fully shipped; R12 needed to reflect the packaging-only progress from the rcpchgrowth side without overclaiming completion. The lifecycle doc was flagged as dense and hard to read before the next planning session.
Verified
git diff --checkpasses