Paul Jolly

It definitely seems like a GitHub bug as opposed to being your fault :)

@dermetfan - welcome to the CUE project! Firstly, thank you for the comprehensive repro. In case you are interested, [the wiki](https://github.com/cue-lang/cue/wiki/Creating-test-or-performance-reproducers) gives some ideas on how you can use the...

@FogDong please can you provide a repro that shows something working on `v0.2.2` and then broken on tip, assuming that is what you are trying to show here?

@FogDong - I think what you are after is: ``` # tip go get cuelang.org/[email protected] go mod tidy go run main.go -- go.mod -- module test-cue/openapi-resolve go 1.17 require cuelang.org/go...

@FogDong that's because the CUE you are trying to parse (the output from the lookup of `#parameter`) is invalid. Instead try something like this: ``` # tip go mod tidy...

I think this is covered off by the conversations we've had in https://github.com/cue-lang/cue/issues/1813#issuecomment-1199687724, but please let me know if not.

Per our discussions in various other issues, I think we have identified a better approach via the `cue.Value` API so I will mark this as closed. Please comment if this...

@seh such non-CUE files cannot, by definition, apply to the command specification, so presumably you are referring to data that is consumed as part of the command execution? If so,...

This is not currently a priority because there are aspects like package management that are higher priority. But we would very much welcome community contributions in this space.

Closing as a dup of #1886, where there is more recent commentary. I will port the example from here over there.