infer coverage query from count query #1478
Draft
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
I had the idea that we could use a parser to collect all the metadata fields and positions accessed in an advanced query, to generate from that a new query that checks that all of these are present - as a baseline to calculate coverage.
I'm not sure if we are really going to need this, but wanted to have the plan ready that I generated with Claude.
View plan: https://github.com/GenSpectrum/LAPIS/blob/2231a9d6adc419353d1483386cfce3aad8d20a98/lapis/claude-plan-coverage-query-builder.md
PR Checklist