-
-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autogenerated schemas not quite as fully-featured as hand-written ones #355
Comments
I figured out that I can add a pattern, by hand-implementing |
Ooh, I can do that too with a hand-crafted implementation. It's all a bit verbose, but do-able. Sorry for the noise! |
Schema generation does not fully support declarative validation rules yet, but some of them are supported. I summarized the current state here: #129 (comment) It also cannot generate structural schema for more complex types ( |
for people wishing to minise their dependencies, add a skip_crd kube attr.
make schema a default compile feature of kube-derive - for #355
@dimbleby : I am happy that you've found a workaround, but we also think you have a point here about people potentially being forced to use a new dependency that they might not need. So, to clarify this issue for future readers; in the next version, |
Hi,
The new schema autogeneration stuff is very interesting. Meanwhile we have been writing schemas by hand: so I am now trying to generate something that is equivalent.
I'm having trouble with a couple of things:
GREsau/schemars#12 looks relevant: but also long inactive.
x-kubernetes-int-or-string: true
. Eg I currently have a field:which makes use of this.
Am I missing a way to achieve these things?
Alternatively, WIBNI to be disable the schema generation. If I'm going to have to write it by hand anyway, why force me to generate it?
Thanks!
The text was updated successfully, but these errors were encountered: