experimental: write component definitions in cue-lang #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is initial foray into what supporting cue with qbec might look like. A component can be written with cue in addition to jsonnet, json and yaml. Implementation is bare-bones and is not production ready Cue packages are supported but not well-tested for mutltiple cases. Brainstorming needed how this would surface in areas like envs, params, etc.
Codecov Report
@@ Coverage Diff @@
## main #283 +/- ##
==========================================
- Coverage 73.80% 73.72% -0.09%
==========================================
Files 73 73
Lines 7021 7079 +58
==========================================
+ Hits 5182 5219 +37
- Misses 1622 1636 +14
- Partials 217 224 +7
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is initial foray into what supporting cue with qbec might look like.
A component can be written with cue in addition to jsonnet, json and yaml. Implementation is bare-bones and is not production ready
Cue packages are supported but not well-tested for mutltiple cases.
Brainstorming needed on how this might surface in areas like envs, params, etc. and if it is a good idea in general