Jeroen Op 't Eynde

From a JSON schema perspective I would expect an object with an `$id` at the root and `$defs` for subschemas. ```json { "$id": "http://example.com/schemas/0.0/team.json", "$schema": "http://json-schema.org/draft-04/schema#", "$defs": { "memberCount": {...

keywords for search: variable substitution

I had a look at this and it seems the built-in jsonnet capabilities do not work well with the server functionality (or I'm doing something wrong and don't understand how...

That's a good proposal, it'd be a first step towards deprecating 'native' jsonnet support from Grizzly

Would you mind splitting of the linter changes into a separate PR?

You can look at the [commit history](https://github.com/jsonnet-libs/k8s-libsonnet/commits/main/), browsing each commit should surface quickly when the last version of 1.23 was created, took me 1min: https://github.com/jsonnet-libs/k8s-libsonnet/tree/5c83a9a2b08fa055cfc62d9f59270161dd729596

@rexagod Anything I can do to help here?

@rexagod Anything I can help to get this merged?

rebased.

rebased and fixed unit test