Skip to content

Support --environment for Up + Fix Exit Status'#150

Merged
JakeCooper merged 3 commits into
masterfrom
cooper/environment-for-each-command
Jul 28, 2021
Merged

Support --environment for Up + Fix Exit Status'#150
JakeCooper merged 3 commits into
masterfrom
cooper/environment-for-each-command

Conversation

@JakeCooper

@JakeCooper JakeCooper commented Jul 27, 2021

Copy link
Copy Markdown
Contributor
  • Supports --environment for up
  • Fixed --environment for run to remove the --environment command wherever it is (Allows you to just run it however you'd like)
  • Fixed exit statuses to actually show the error message instead of swallowing

@JakeCooper JakeCooper changed the title Support --environment for Up Support --environment for Up + Fix Exit Status' Jul 27, 2021
Comment thread cmd/open.go
return err
}
environmentId, err := h.cfg.GetEnvironment()
environmentId, err := h.cfg.GetCurrentEnvironment()

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason most of the commands call GetEnvironment() as opposed to GetEnvironment to use the environment from flag if it exists?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't follow? if you're asking why GetEnvironment doesn't just use the flags cause then we'd have to alter it to take the Cmd as a param and when I did it it was nasty

Still not thritted with this implementation but at least it's clear

@JakeCooper
JakeCooper merged commit 259d5c4 into master Jul 28, 2021
@JakeCooper
JakeCooper deleted the cooper/environment-for-each-command branch July 28, 2021 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants