This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
cmd/cue: make it possible for import to operate on standard input #116
Labels
FeatureRequest
New feature or request
good first issue
Good for newcomers
roadmap/cli
Specific tag for roadmap issue #337
Milestone
Comments
mpvl
added
FeatureRequest
mpvl
added a commit
that referenced
this issue
Feb 17, 2020
The idea is that the build.File type will be added to the build.Instance type, replacing the current file specs. It will be populated by the load package. The command line tool can subsequently use this package to determine settings on how to interpret build.File. It is a separate internal package so that the API can be shared by load and cmd. Issue #280 Issue #254 Issue #183 Issue #130 Issue #116 Change-Id: I47f2391945113fe664f0ec33b0048be70326edb5 Reviewed-on: https://cue-review.googlesource.com/c/cue/+/4946 Reviewed-by: Marcel van Lohuizen <mpvl@golang.org> Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
Closed
|
This issue has been migrated to cue-lang/cue#116. For more details about CUE's migration to a new home, please see cue-lang/cue#1078. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, it's possible to ask
cue importto produce the result to the standard output, but there's no way to tell it to read from standard input.It's not possible to do
cue import /dev/stdinbecause/dev/stdindoesn't have a file extension.As a corollary to this, it would be nice to be able to import files that don't have the conventional file extension, particularly when specifying the file names directly on the command line.
Perhaps a
-ext jsonflag ("treat all files as if their extension was JSON") might work, or perhaps--force-type(-Ffor short?) ("treat all files as if their extension is as declared by the-typeflag").The text was updated successfully, but these errors were encountered: