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

Document BC break #9143

Merged
merged 1 commit into from
Oct 30, 2021
Merged

Document BC break #9143

merged 1 commit into from
Oct 30, 2021

Conversation

greg0ire
Copy link
Member

Closes #9141

I'm not great at assessing the severity of BC-breaks, so please do tell if you feel we should revert #8837 , or if you have an idea to somehow make both things work without affecting performance too much.

cc @franmomu

@derrabus derrabus added this to the 2.10.3 milestone Oct 21, 2021
Copy link
Contributor

@franmomu franmomu left a comment

Choose a reason for hiding this comment

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

👍 I'll try to make it work with another approach

@derrabus derrabus merged commit 16cbc16 into doctrine:2.10.x Oct 30, 2021
@greg0ire greg0ire deleted the document-bc-break branch November 3, 2021 20:16
@stof
Copy link
Member

stof commented Nov 17, 2021

@greg0ire a way to provide a BC layer would be to detect cases passing a string as argument instead of an int, and converting the object hash to an object id (and triggering a deprecation of course). the logic for that is available in the implementation of the spl_object_id polyfill (as that's exactly how the polyfill is implemented)

@greg0ire
Copy link
Member Author

Good to know! I'll reuse it if anyone else complains about this.

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.

spl_object_hash() vs spl_object_id()
4 participants