Reference ClassMetadaInfo less #9691
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Although properties and methods are currently located in ClassMetadataInfo, it is better to refer to ClassMetadata as the former is deprecated in favor of the latter.
This documentation must be very old because this is no longer valid as of e9e36dc . The interface and abstract file driver have since then been moved to doctrine/common, and the to doctrine/persistence.
ClassMetadataInfo used to be useful during entity generation, because it allowed the entity not to exist. We no longer do entity generation, and even if we did, the reflection methods have been moved to ClassMetadataInfo as of 76e4f5a .
derrabus
approved these changes
Apr 28, 2022
This was referenced Apr 28, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #6886, I proposed an upgrade path from
ClassMetadataInfotoClassMetadata. The PR has gathered a lot of discussion, and cobwebs. This PR aims to take care of a small part of it: documentation. It's a great place to start since it allows to understand whyClassMetadataInfoexisted in the first place.See #314 and #249