-
Notifications
You must be signed in to change notification settings - Fork 351
Open
Labels
FeatureRequestNew feature or requestNew feature or requestget goissues related to cue get goissues related to cue get go
Description
Originally opened by @myitcv in cuelang/cue#646
Splitting out a separate issue for the rename of get go to import go from cuelang/cue#621 (comment)
Other points to consider:
- whether
cue import goshould adoptgo test-like behaviour of making progress where it can. For example, if you runcue import go ./...and one package in the set that is matched by./...fails to type check, then we should generate definitions for those packages that do type check rather than failing the entire process cue get gohas a--localflag. In a world of modules this flag is, I think, redundant. Because if you were to runcue import goon a main module package, it would be strange for it to be placed within thecue.mod/hierarchy. It only makes sense for such definitions to be generated alongside the Go code from which they were generated. Fixes cmd/cue: path resolution issue for get go generated files #452cue import goshould run withGOFLAGS=-mod=readonlyto enforce that all dependencies are available- Fix the redundant walking of target package directories for
.cuefiles (happens as part of the walk of the directories containingCompiledGoFiles) - Fix the fact that generated code should be placed in the
cue.mod/genhierarchy, not thecue.mod/pkgas it is today - Consider supporting
cue import go $pkg@$version. This allows people to depend on a package (or packages) outside the dependency graph of their main module.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
FeatureRequestNew feature or requestNew feature or requestget goissues related to cue get goissues related to cue get go