-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unifying incomplete CUE and concrete data, using the cue
command and the Go API
#180
Labels
content idea
Idea for a new piece of content
howto
For content that in the "howto" diataxis quadrant
Comments
jpluscplusm
added
content idea
Idea for a new piece of content
howto
For content that in the "howto" diataxis quadrant
labels
Oct 3, 2024
cueckoo
pushed a commit
to cue-lang/cuelang.org-trybot
that referenced
this issue
Oct 25, 2024
WIP Fixes cue-lang/docs-and-content#180. Preview-Path: /docs/concept/working-with-incomplete-cue Signed-off-by: Paul Jolly <[email protected]> Change-Id: If2fdd49e42c96cd098a19464038827ad2000e951 Dispatch-Trailer: {"type":"trybot","CL":1203092,"patchset":2,"ref":"refs/changes/92/1203092/2","targetBranch":"master"}
cueckoo
pushed a commit
to cue-lang/cuelang.org-trybot
that referenced
this issue
Oct 25, 2024
WIP Fixes cue-lang/docs-and-content#180. Preview-Path: /docs/concept/working-with-incomplete-cue Signed-off-by: Paul Jolly <[email protected]> Change-Id: If2fdd49e42c96cd098a19464038827ad2000e951 Dispatch-Trailer: {"type":"trybot","CL":1203092,"patchset":3,"ref":"refs/changes/92/1203092/3","targetBranch":"master"}
cueckoo
pushed a commit
to cue-lang/cuelang.org-trybot
that referenced
this issue
Oct 28, 2024
This adds a concept guide explaining the basics of working with incomplete CUE using both the cue command and the Go API. Fixes cue-lang/docs-and-content#180. Preview-Path: /docs/concept/working-with-incomplete-cue Signed-off-by: Paul Jolly <[email protected]> Change-Id: If2fdd49e42c96cd098a19464038827ad2000e951 Dispatch-Trailer: {"type":"trybot","CL":1203092,"patchset":5,"ref":"refs/changes/92/1203092/5","targetBranch":"master"}
cueckoo
pushed a commit
to cue-lang/cuelang.org-trybot
that referenced
this issue
Oct 28, 2024
This adds a concept guide explaining the basics of working with incomplete CUE using both the cue command and the Go API. Fixes cue-lang/docs-and-content#180. Preview-Path: /docs/concept/working-with-incomplete-cue Signed-off-by: Paul Jolly <[email protected]> Change-Id: If2fdd49e42c96cd098a19464038827ad2000e951 Dispatch-Trailer: {"type":"trybot","CL":1203092,"patchset":6,"ref":"refs/changes/92/1203092/6","targetBranch":"master"}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
content idea
Idea for a new piece of content
howto
For content that in the "howto" diataxis quadrant
Slack thread: https://cuelang.slack.com/archives/CLT3ULF6C/p1718013879866749
Original Slack thread conclusion
myitcv
In general, CUE can deal with references to fields that don't exist (yet)
e.g.
This is referred to as incomplete CUE.
Such CUE cannot be exported, but it can be evaluated.
It can also be made complete by unifying it with a value that makes it complete.
Here, step1 could be the result of a first load, for example
step2 could come from anywhere else
res is the result of unifying the two.
Here's a quick demo
The idea being that we can show how to work with incomplete values and unification (the simplest of pipelines) to make things concrete.
The text was updated successfully, but these errors were encountered: