Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.6k
[Console] Define isVerbose(), etc. methods in OutputInterface#13086
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
👍 This was indeed on our list of changes for 3.0 |
@stof Didn't know. Where do I find that list? |
| * | ||
| * @return bool true if verbosity is set to VERBOSITY_QUIET, false otherwise | ||
| * | ||
| * @api |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
We don't add that yet.
Will reopen that once there is a 3.0 branch... |
@frne Why did you close? |
@Tobion For my comprehension: You want me to remove the |
@frne yes |
Thank you@frne. |
…terface (frne)This PR was squashed before being merged into the 3.0-dev branch (closes#13086).Discussion----------[Console] Define isVerbose(), etc. methods in OutputInterfaceCould / should the ```Symfony\Component\Console\Output\OutputInterface``` define the methods ```isQuiet()```, ```isVerbose()```, ```isVeryVerbose()``` and ```isDebug()```?Because the Interface already defines the verbosity constants and the ```getVerbosity()``` method, it will probalby be the right place to do so...| Q | A| ------------- | ---| Bug fix? | no| New feature? | no| BC breaks? | yes| Deprecations? | no| Tests pass? | yes| Fixed tickets || License | MIT| Doc PR |Commits-------1ac95b1 [Console] Define isVerbose(), etc. methods in OutputInterface
Could / should the
Symfony\Component\Console\Output\OutputInterfacedefine the methodsisQuiet(),isVerbose(),isVeryVerbose()andisDebug()?Because the Interface already defines the verbosity constants and the
getVerbosity()method, it will probalby be the right place to do so...