recipe-driven FHIR column selection - #24
Draft
matthewpeterkort wants to merge 3 commits into
Draft
Conversation
Contributor
Author
|
Retaining this as the second warm-storage idea. The recipe-driven column-selection concept is valuable, but this stacked branch is not planned for merge as-is. Future revival should start from current #17 and selectively port the candidate API, selection modes, and runtime behavior. The head branch is preserved. |
matthewpeterkort
marked this pull request as draft
August 19, 2026 18:18
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
1 participant
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.
Stacks on #22.\n\nAdds backward-compatible DISCOVER/SELECTED column modes for dynamic columns, extension columns, and pivots; SELECTED empty lists materialize zero columns at root or nested traversal nodes.\n\nAdds the authorized, recipe-aware dataframeRecipeColumnCandidates GraphQL connection with traversal alias paths, stable raw-key identities, native patch targets, public names, semantic examples/population/type/cardinality, selected state, pagination, stale-selection reporting, and blocking completeness diagnostics.\n\nExisting recipes that omit columnMode keep discovery behavior. No HTAN-specific keys or values are hardcoded.\n\nValidation: go test ./... -count=1 (1835 passed); make graphql-check.