CUE Roadmap Alignment

[sdboyer]

To help the CUE folks decide what they ought work on next, we'll use this issue to highlight the things scuemata would most benefit from progress on.

Cleaner API for working with cue.Value

This is kinda broad-strokes, but we currently do absolutely unholy things in this project to achieve our desired generated Typescript results. N.B., it's possible that we're just approaching this problem space all wrong, and should be relying on more of a backbone of syntactic analysis (ast package) rather than almost entirely semantic (cue package).

• Representing everything as a cue.Value gets really confusing when you're deep in the weeds of teasing out an .Expr()
• Differentiating between a selector with a subject that's an import vs. a local-file struct is extremely, almost prohibitively difficult

Replacement for cue.Instance

Recent versions of CUE deprecated cue.Instance. In general, we prefer operating on cue.Value, as it allows us to grant flexible control to the cuetsy consumer about exactly what's getting converted. (This is essential for scuemata, where we want to convert only the latest schema, not the whole logical structure)

We need to be able to inspect imports in order to generate corresponding typescript imports, and being able to reach back up to them from a cue.Value - or whatever successor to it exists - is key to being able to make a nice, tight API for cuetsy.