8000 exception during a command: more specific explanation of the behaviour by bruno-ds · Pull Request #10719 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

exception during a command: more specific explanation of the behaviour #10719

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

Closed
wants to merge 3 commits into from

Conversation

bruno-ds
Copy link
Contributor

This section wasn't specific about the new behavior.

I added an explanation copy/pasted from symfony's blog explanation : https://symfony.com/blog/new-in-symfony-3-3-automatic-console-logging

This section wasn't specific about the new behav
8000
ior.

I added an explanation copy/pasted from symfony's blog explanation : https://symfony.com/blog/new-in-symfony-3-3-automatic-console-logging
Copy link
Contributor
@OskarStark OskarStark left a comment

Choose a reason for hiding this comment

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

Please linebreak

Co-Authored-By: bruno-ds <bruno-ds@users.noreply.github.com>
Co-Authored-By: bruno-ds <bruno-ds@users.noreply.github.com>
@bruno-ds
Copy link
Contributor Author

Thank you @OskarStark, I applied your two suggested changes

@javiereguiluz
Copy link
Member

@bruno-ds thanks for contributing this proposal. I like it ... but it's been added to an article that we'd prefer to remove because it's no longer relevant. So, inspired by your contribution, I've created #10897 to remove this article and put this new doc inside the main Console article.

That's why I'm closing this without merging, but I hope you understand it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0