-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
refactor(cmd/root): simplify parseEnvs
#2162
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@Juneezee this pull request has failed checks 🛠 |
@Juneezee this pull request has failed checks 🛠 |
Prior to this commit, `parseEnvs` accept two parameters: 1. env []string 2. envs map[string]string `parseEnvs` then do a `nil` check for `env`. However, we never pass a `nil` `env` to `parseEnvs` in `newRunCommand`. This commit simplify the `parseEnvs` function to accept just one `env []string` parameter and return the result as `map[string]string` instead. Signed-off-by: Eng Zer Jun <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2162 +/- ##
==========================================
- Coverage 61.22% 60.90% -0.33%
==========================================
Files 46 53 +7
Lines 7141 8990 +1849
==========================================
+ Hits 4372 5475 +1103
- Misses 2462 3074 +612
- Partials 307 441 +134 ☔ View full report in Codecov by Sentry. |
wolfogre
approved these changes
Jan 24, 2024
cplee
approved these changes
Jan 24, 2024
jmikedupont2
pushed a commit
to meta-introspector/act
that referenced
this pull request
Mar 10, 2024
Prior to this commit, `parseEnvs` accept two parameters: 1. env []string 2. envs map[string]string `parseEnvs` then do a `nil` check for `env`. However, we never pass a `nil` `env` to `parseEnvs` in `newRunCommand`. This commit simplify the `parseEnvs` function to accept just one `env []string` parameter and return the result as `map[string]string` instead. Signed-off-by: Eng Zer Jun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently
parseEnvs
accept two parameters:env []string
envs map[string]string
parseEnvs
then do a safetynil
check forenv
.act/cmd/root.go
Lines 299 to 312 in 15bb54f
However, we never pass a
nil
env
toparseEnvs
innewRunCommand
.act/cmd/root.go
Lines 417 to 418 in 15bb54f
act/cmd/root.go
Lines 422 to 423 in 15bb54f
This commit simplify the
parseEnvs
function to accept just oneenv []string
parameter and return the result asmap[string]string
instead.