Kévin Gomez
Kévin Gomez
When a dataquery is successfully identified by the `DataqueryIdentification` compiler pass, it should update the schema metadata to reflect that fact. Possible alternative to #398
Instead of relying on `./schemas/composable/prometheus` for Grafana versions >= v11, we need to find a schema published and maintained by Grafana itself. Schema removed by: https://github.com/grafana/grafana/pull/83808 Possible replacement? https://github.com/grafana/grafana/blob/main/pkg/promlib/models/query.request.schema.json This...
There is a lot of complexity shared across jennies/languages to work with defaults. We should look into how these can be better modeled and how we can simplify the work...
It's really easy to have inconsistent formatting for identifiers (type names, variables, classes, fields, ...) This processing is split across various places: different jennies and templates mainly. What about applying...
There is no schema for this panel type. It would be a useful addition to the foundation-sdk: we need to either produce a schema ourselves, or ask the relevant team...
Our jennies do not sanitize package names enough, so if a package contains dashes it will be rendered as-is in the generated code, which is a problem for most languages....
Mostly some renamings, to make the imports management more understandable. Imports are also now sorted, to ensure a reproducible output
Kind of the opposite from what a builder does (code → JSON), it would be a useful improvement in terms of DX to be able to convert JSON to the...
See https://devguide.python.org/versions/ This jenny currently generates code that requires Python >= 3.11. We should consider extending support for older versions as well (maybe up to 3.8?)
In candlestick: ```cue CandlestickColors: { up: string | *"green" down: string | *"red" flat: string | *"gray" } Options: { colors: CandlestickColors | *{ down: "red" up: "green" flat: "gray"...