[2.x] Fixes missing output while using execute option #109
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
|
I suppose this shows nobody is using the execute option. Could we remove it? |
|
@GrahamCampbell We are using it in Vapor. |
|
;) |
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.
When using tinker with the
executeoption, the output instance is missing on the $shell instance. Causing tinker not being able to show exceptions to the user. You can quickly reproduce this bug in a fresh Laravel application like so:Gives the following error:
Error: Call to a member function writeln() on null.After this chance, you will get the expected output:
Exception with message 'Foo'.