Helder Correia

Thanks @mpvl, the intent is to type a structure like this (i.e., variable key depth, ending in a `$secret`): ```cue { FOO: { $secret: {} } ONE: { TWO: {...

I attempted this, but isn't working in practice: ``` exec cue eval x.cue -- x.cue -- src: { #Secret: { $secret: _id: string } a: { output: _#out _#out: #Secret...

@eonpatapon We're filling with `cue.Hid()`: ```go var secretIDPath = cue.MakePath( cue.Str("$dagger"), cue.Str("secret"), cue.Hid("_id", pkg.DaggerPackage), ) // ... v.FillPath(secretIDPath, s.id) ``` https://github.com/dagger/dagger/blob/b4f934a6ea2d9787fb66bf2cbfac8d4f9ded4141/plancontext/secret.go#L39 Wouldn't this be a better representation? ``` exec cue...

My example works even in current version, as you can see in the output, but just in CUE. When I say it doesn't work in "practice" I mean in Dagger.

Sorry @myitcv, I should have been clearer, there's actually two errors we're dealing with here. This is how this progressed: 1. Structural cycle cause by `output: #Secret | {[string]: output}`...

I just referenced a few issues from dagger. Users are getting confused because typos are leading to unexpected errors elsewhere and it's hard to understand why. At least now I...

> @helderco please can you provide examples of the issues people are seeing in Dagger? We should categorise them to ensure they are either covered by the cases described in...

Yes I planned on doing that today but I just haven’t been able to get to it yet.

There's an example from: - https://github.com/cue-lang/cue/issues/1611 - https://github.com/dagger/dagger/issues/1885#issuecomment-1081780957 ``` exec cue cmd actions -- main_tool.cue -- package main import "tool/cli" command: { actions: { a: cli.Print & { $before: [actions.b]...

Here's an _incomplete cause disjunction_ we're seeing. ``` exec cue eval x.cue -c -- cue.mod/module.cue -- module: "example.com" -- fn/fn.cue -- package fn #M: { t: "s" c: string }...