You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
These are implemented as tasks as they are state
altering and may yield different results on repeated
calls.
Also:
- Remove usage of package errors for pkgs.
- Updated go-cmp
- Fix bug in dependency analysis where default
values could cause a dependency to be concrete
prematurely.
Issue #159
Change-Id: I517eb6892cbeff538c806a822510ffce5dcb31b0
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/4461
Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
The tooling layer now supports environment variables.
A general mechanism for injecting values based on command lines flags is now supported through --inject/-t. This is not general command line flags, which may still be considered, but it is actually surprisingly hard to get a nice UX for. So closing this for now until --inject/-t proves insufficient.
To what extent should environment variables and flags be unified?
How should the cmd command evaluate environmental variables and flags when both are specified.
The text was updated successfully, but these errors were encountered: