Repository navigation
refactor: standardize exec_from funcs arg order - #8809
Merged
Merged
Conversation
7 tasks
Contributor
Author
|
Thanks, yeah, I agree. If a good approach comes to mind as I'm using it, I'll open another PR. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
Closes #8808
Rationale for this change
For me the order of 'what does the execing, what's exec'd, then options` makes sense to me, but overally the goal of this PR is to make the order consistent.
Are these changes tested?
Manual testing of built CLI, open to other options
Are there any user-facing changes?
Not sure how many are using the CLI code in their own projects, but this could break their code (albeit with an easy fix).