Skip to content

[ErrorRenderer] extend legacy exception for backwards compatibility #33981

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

Merged
merged 1 commit into from
Oct 15, 2019

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Oct 14, 2019

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

@xabbuh xabbuh added this to the next milestone Oct 14, 2019
@xabbuh xabbuh requested a review from yceruto as a code owner October 14, 2019 13:13
@xabbuh xabbuh force-pushed the pr-33941 branch 2 times, most recently from 83450a3 to 6c1e244 Compare October 14, 2019 13:17
Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

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

We tried hard not doing so but we have to face the truth, that's the only way :)

Copy link
Member

@yceruto yceruto left a comment

Choose a reason for hiding this comment

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

👍 we should also update the HttpKernel\...\ExceptionListener class according to this approach.

@@ -39,12 +40,12 @@ class FlattenException
private $file;
private $line;

public static function create(\Exception $exception, int $statusCode = null, array $headers = []): self
public static function create(\Exception $exception, $statusCode = null, array $headers = []): self
Copy link
Member

Choose a reason for hiding this comment

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

: LegacyFlattenException?

@yceruto
Copy link
Member

yceruto commented Oct 14, 2019

Just asking: Did you find another BC break? Won't #33941 be enough to keep the BC?

@nicolas-grekas
Copy link
Member

Just asking: Did you find another BC break? Won't #33941 be enough to keep the BC?

see 3.4 and 4.3 in https://travis-ci.org/symfony/symfony/builds

@yceruto yceruto force-pushed the pr-33941 branch 2 times, most recently from 94c0a72 to 7432e68 Compare October 14, 2019 22:00
@xabbuh
Copy link
Member Author

xabbuh commented Oct 15, 2019

Status: Needs Review

@nicolas-grekas
Copy link
Member

Thank you @xabbuh.

nicolas-grekas added a commit that referenced this pull request Oct 15, 2019
…atibility (xabbuh)

This PR was merged into the 4.4 branch.

Discussion
----------

[ErrorRenderer] extend legacy exception for backwards compatibility

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

Commits
-------

71a0b9b extend legacy exception for backwards compatibility
@nicolas-grekas nicolas-grekas merged commit 71a0b9b into symfony:4.4 Oct 15, 2019
@xabbuh xabbuh deleted the pr-33941 branch October 15, 2019 13:41
@nicolas-grekas nicolas-grekas modified the milestones: next, 4.4 Oct 27, 2019
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