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

Remove inheritance #11142

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Remove inheritance #11142

merged 1 commit into from
Jan 2, 2024

Conversation

greg0ire
Copy link
Member

Spotted while trying to merge #11076 (among other things) up into 3.0.x. On that branch, it is no longer possible for an entity to extend another entity without specifying an inheritance mapping type.

I think the goal of that inheritance was just to reuse the identifier anyway, so let's just duplicate the identifier declaration instead.

Spotted while trying to merge doctrine#11076
(among other things) up into 3.0.x. On that branch, it is no longer
possible for an entity to extend another entity without specifying an
inheritance mapping type.

I think the goal of that inheritance was just to reuse the identifier
anyway, so let's just duplicate the identifier declaration instead.
@greg0ire
Copy link
Member Author

Cc @norkunas

@norkunas
Copy link
Contributor

Sorry :)

@greg0ire
Copy link
Member Author

No worries, just wanted to be sure there was nothing necessary with that inheritance :)

@greg0ire greg0ire merged commit 26f47cb into doctrine:2.17.x Jan 2, 2024
54 checks passed
@greg0ire greg0ire deleted the remove-inheritance branch January 2, 2024 07:24
@greg0ire greg0ire added this to the 2.17.3 milestone Jan 2, 2024
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.

3 participants