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

Address commonexception deprecation #397

Merged

Conversation

MarcBrillault
Copy link
Contributor

No description provided.

This is what we do on other doctrine packages.
The exception we were extending is deprecated.
Copy link
Member

@SenseException SenseException left a comment

Choose a reason for hiding this comment

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

Looks good, but @greg0ire how are BC breaks handled in this repo that 1.5 to 1.6 introduce them?

@greg0ire
Copy link
Member

@SenseException Marc is my colleague, and we wrote this PR together. In particular, this sentence: "We don't think anyone catches this exception in a catch (CommonException) statement". It's my personal opinion that a BC-break is OK in this case. If you feel otherwise, we can create 2.0.x and retarget to that.

@SenseException
Copy link
Member

I see data-fixtures mostly in a dev env in projects, which is why I approved the PR. I wanted to be sure that nothing was missed with these changes and that the chosen version was on purpose.

@greg0ire greg0ire merged commit 3645024 into doctrine:1.6.x Jun 17, 2022
@greg0ire
Copy link
Member

Thanks @MarcBrillault !

@greg0ire greg0ire added this to the 1.6.0 milestone Jun 17, 2022
@MarcBrillault MarcBrillault deleted the address-commonexception-deprecation branch June 17, 2022 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants