-
Notifications
You must be signed in to change notification settings - Fork 566
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
Register JSON schema with SchemaStore #4751
Comments
Flux has full support in JetBrains IDEA, all you need is to add the CRDs to the Kubernetes plugin, see: As for VSCode, we publish the OpenAPI spec for all our CRDs here: https://github.com/fluxcd-community/flux2-schemas |
Thank you so much for the additional information @stefanprodan and taking the time to comment. That is very helpful. Would you be open to adding Flux's schemas to SchemaStore? As you can provide a pointer in their repository (here: |
I'm not sure how this would work, there is no |
Following through a similar example with the OpenRewrite project that might alleviate the concern for no Then they pointed to this schema generically in SchemaStore like so: Add schema for OpenRewrite resource descriptors
|
Describe the bug
Flux does not have code completion or basic validation support in IDEs and editors such as VS Code, JetBrains IDEA, etc.
Steps to reproduce
Make an invalid change anywhere in Flux in VS Code or JetBrains IDEA and the IDE will not provide basic validation.
Expected behavior
By registering the existing JSON schemas in the generated
crd-schemas
with https://github.com/SchemaStore/schemastore it should automatically be picked up by many of the supporting IDEs and editors such as VS Code, JetBrains IDEA, etc. This would be extremely useful when using Flux as it offers code completion and basic validation for editors.Screenshots and recordings
No response
OS / Distro
N/A
Flux version
N/A
Flux check
N/A
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: