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 deprecations from Collection 2.2 #11315

Merged
merged 1 commit into from Feb 27, 2024

Conversation

derrabus
Copy link
Member

@derrabus derrabus commented Feb 27, 2024

Part of #11313.

@derrabus derrabus added the Bug label Feb 27, 2024
@derrabus derrabus added this to the 2.18.2 milestone Feb 27, 2024
@derrabus derrabus force-pushed the bugfix/collections-deprecations branch 3 times, most recently from 22d9e83 to f6ad8d5 Compare February 27, 2024 13:42
greg0ire
greg0ire previously approved these changes Feb 27, 2024
@greg0ire
Copy link
Member

"Bug" is not really the right label, is it?

@derrabus derrabus force-pushed the bugfix/collections-deprecations branch from 013726b to 61736af Compare February 27, 2024 14:16
@derrabus
Copy link
Member Author

"Bug" is not really the right label, is it?

The current code triggers deprecations that it should not trigger. That is a bug. But we can reclassify if you're not comfortable shipping this change as a bugfix.

@greg0ire
Copy link
Member

greg0ire commented Feb 27, 2024

I'm comfortable shipping it in a patch release, but I think we might want to have a separate label for when we address deprecations, like maybe "Addressed deprecation" (can't think of something better right now, sorry). If we say it's a bug, it means other packages can decide to cause bugs in our projects from one release to the next minor release, although we did nothing wrong.

@derrabus
Copy link
Member Author

If we say it's a bug, it means other packages can decide to cause bugs in our projects from one release to the next minor release, although we did nothing wrong.

"Bug" is a totally blame-free word for me. I never said the we could've anticipated the issue that I've fixed here.

@greg0ire
Copy link
Member

I think that makes some sense. Ignore me then.

@derrabus derrabus merged commit feb27f0 into doctrine:2.18.x Feb 27, 2024
58 checks passed
@derrabus derrabus deleted the bugfix/collections-deprecations branch February 27, 2024 16:37
derrabus added a commit to derrabus/orm that referenced this pull request Feb 29, 2024
* 3.0.x:
  PHPStan 1.10.59 (doctrine#11320)
  Address deprecations from Collection 2.2 (doctrine#11315)
  Fix sql walker phpdoc
derrabus added a commit to derrabus/orm that referenced this pull request Mar 1, 2024
* 3.1.x:
  PHPStan 1.10.59 (doctrine#11320)
  Address deprecations from Collection 2.2 (doctrine#11315)
  Deprecate invalid method call
  Throw a full-fledged exception on invalid call
  Remove extra word
  Fix sql walker phpdoc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants