Skip to content

cmd/cue: richer configurability of encodings #3888

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

Open
rogpeppe opened this issue Apr 9, 2025 · 0 comments
Open

cmd/cue: richer configurability of encodings #3888

rogpeppe opened this issue Apr 9, 2025 · 0 comments
Labels
encoding FeatureRequest New feature or request

Comments

@rogpeppe
Copy link
Member

rogpeppe commented Apr 9, 2025

The filetypes syntax (e.g. cue+jsonschema:) is nicely concise to use on the command line, but
as encodings become more complex, it is quite limited and does not scale well.
For example, it would be useful to be able to specify URI to package mappings when
importing JSON Schema, but the simple tag=value syntax of filetypes would probably not
be up to that job. We'd end up needing to define quoting syntax etc, but we already have
a config language that is up to the job: CUE itself.

I suspect the right answer is to do something similar to CUE_REGISTRY: support the existing
simple syntax as syntax sugar for a richer format that can be specified in CUE (in CUE_REGISTRY
that's done with file: and we could do something similar).

@rogpeppe rogpeppe added encoding FeatureRequest New feature or request labels Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
encoding FeatureRequest New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant