[PoC] Use cog to generate go and typescript models + resources #296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft PR meant to try out cog as a potential replacement for Go and Typescript codegen purposes.
ToDo:
thema.CustomKindParser
provided bygrafana-app-sdk
used with cog's CUE parser struggle to correctly handle references to objects defined "above" the currently parsed root. Ex:InnerObject2
(something likecustomKind.lineage._sortedSchemas[1]._#schema.#InnerObject2
), but resolving this path (withLookupPath()
fails on hidden fields introduced by thema (_sortedSchemas
and_#schema
).If thema support isn't meant to stick around long-term, this issue might not be worth solving.
Note: this PR isn't necessarily meant to be finished or merged, it's more a sandbox to play with cog + grafana-app-sdk.