Repository navigation
feat: lookup where null - #337
Merged
Merged
Conversation
Signed-off-by: Sarah Funkhouser <147884153+golanglemonade@users.noreply.github.com>
golanglemonade
force-pushed
the
feat-extract-schema-annotation
branch
from
October 14, 2026 18:36
09b9968 to
48b9354
Compare
golanglemonade
changed the title
golanglemonade
marked this pull request as ready for review
October 18, 2026 21:19
golanglemonade
enabled auto-merge (squash)
October 18, 2026 21:20
|
adelowo
approved these changes
Oct 21, 2026
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
2 participants
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.
LookupWhereNullto support schemas like controls where we want to follow the same unique constraint of ref_code + framework, but there is a case where framework is null that is allowed