-
Notifications
You must be signed in to change notification settings - Fork 21
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
--context
option ignored when another option precedes it
#593
Comments
After some debug, it seem like we attempt to bind application definition, but when we are binding the application to input, application definition doesn't declare those from task, and this was silented by try/catch block in Lines 206 to 224 in 902c05d
|
TheoD02
added a commit
to TheoD02/castor
that referenced
this issue
Dec 19, 2024
TheoD02
added a commit
to TheoD02/castor
that referenced
this issue
Dec 19, 2024
TheoD02
added a commit
to TheoD02/castor
that referenced
this issue
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to use the
--context
option to select a specific context, it works as expected unless another option is declared before the--context
option.Example Setup
Steps to Reproduce
Run the following command:
Result: Works as expected. Running
context()->name
outputssymfony
.Run the same command but with an additional option before
--context
:Result:
context()->name
unexpectedly outputsdefault
instead ofsymfony
.Change the order of the options, placing
--context
before--force
:Result: Works as expected, and
context()->name
outputssymfony
.Expected Behavior
Regardless of the order of the options, specifying
--context
should correctly set the context.Actual Behavior
If another option precedes
--context
, the context is ignored, and the default context is used.Environment
The text was updated successfully, but these errors were encountered: