Skip to content
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

[FrameworkBundle][ContainerLintCommand] Style messages #34865

Merged
merged 1 commit into from Jan 10, 2020

Conversation

fancyweb
Copy link
Contributor

@fancyweb fancyweb commented Dec 6, 2019

Q A
Branch? master
Bug fix? no
New feature? yes
Deprecations? no
Tickets -
License MIT
Doc PR -

It gives a better feedback.

$container->compile();
try {
$container->compile();
} catch (InvalidArgumentException $e) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we check if the exception was thrown in CheckTypeDeclarationsPass?

@chalasr chalasr modified the milestones: 4.4, next Dec 7, 2019
@fancyweb fancyweb force-pushed the fwb-lint-command-fail-properly branch 2 times, most recently from 15187b1 to 05428f2 Compare December 10, 2019 13:35
@fancyweb fancyweb changed the base branch from 4.4 to master December 10, 2019 13:35
@fancyweb
Copy link
Contributor Author

I rebased on master as this is a new behavior.

fabpot added a commit that referenced this pull request Dec 16, 2019
… when the kernel or the container is not supported (fancyweb)

This PR was merged into the 4.4 branch.

Discussion
----------

[FrameworkBundle][ContainerLintCommand] Improve messages when the kernel or the container is not supported

| Q             | A
| ------------- | ---
| Branch?       | 4.4
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Tickets       | #34865 (comment)
| License       | MIT
| Doc PR        | -

Minor wording suggested here #34865 (comment)

Commits
-------

6986394 [FrameworkBundle][ContainerLintCommand] Improve messages when the kernel or the container is not supported
@fancyweb fancyweb force-pushed the fwb-lint-command-fail-properly branch from 05428f2 to cb010e9 Compare December 17, 2019 13:13
Copy link
Contributor

@ro0NL ro0NL left a comment

Choose a reason for hiding this comment

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

much appreciated :)

@fancyweb fancyweb force-pushed the fwb-lint-command-fail-properly branch from cb010e9 to 93aa5bc Compare January 2, 2020 11:33
fabpot added a commit that referenced this pull request Jan 7, 2020
…positive feedback on stderr (fancyweb)

This PR was merged into the 3.4 branch.

Discussion
----------

[FrameworkBundle][TranslationUpdateCommand] Do not output positive feedback on stderr

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | #34865 (comment)
| License       | MIT
| Doc PR        | -

Outputing everything on stderr seems wrong. I'm going to check upper branches.

Commits
-------

87212e4 [FrameworkBundle][TranslationUpdateCommand] Do not output positive feedback on stderr
@fabpot
Copy link
Member

fabpot commented Jan 10, 2020

Thank you @fancyweb.

fabpot added a commit that referenced this pull request Jan 10, 2020
… (fancyweb)

This PR was merged into the 5.1-dev branch.

Discussion
----------

[FrameworkBundle][ContainerLintCommand] Style messages

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

It gives a better feedback.

Commits
-------

93aa5bc [FrameworkBundle][ContainerLintCommand] Style messages
@fabpot fabpot merged commit 93aa5bc into symfony:master Jan 10, 2020
@nicolas-grekas nicolas-grekas modified the milestones: next, 5.1 May 4, 2020
@fabpot fabpot mentioned this pull request May 5, 2020
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.

None yet

6 participants