sam boyer

When talking all this through with @Lyoness and @myitcv earlier today, i realized that this, the possibility of adding the `themaVersion?` field, and #76 can be taken care of all...

Let's keep it open. I think there's a way we incorporate this with other in-flight work.

FWIW the [JSON Schema encoding package in Thema](https://pkg.go.dev/github.com/grafana/[email protected]/encoding/jsonschema#GenerateSchema) amounts to a generic CUE->JSON Schema converter - it takes OpenAPI 3.0 output (as produced by the cue stdlib openapi encoder) and...

This is gonna take some discussion before starting - probably needs a design doc.

Note that this: > Line-level information about errors is deceptively tricky. On the one hand, CUE very _awesomely_ carries line-level traceability for validation errors by construction. But there are caveats....

cc @ryantxu

With the shift back to k8s, this is no longer a goal.

just fully processed this bit: > This is an example where we can save items that do not have a clear folder structure in the entity store This is saying...

> pretty sure it needs to be above all that at the entity/summary/metadata level. It's kind metadata, which in turn drives entity metadata. That's where it needs to live, or...

This is why nailing this stuff down, _soon_, is so important. Happily, with kindsys in place, doing so is relatively straightforward. So long as there is no use case in...