Class metadata loading fallback hook#342
Merged
Ocramius merged 3 commits intodoctrine:masterfrom Jan 13, 2015
Merged
Conversation
… operations when failing to load class metadata
…ailed due to mapping exceptions (typically not-found class)
|
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DCOM-257 We use Jira to track the state of pull requests and the versions they got |
Member
Author
|
Merging as per @guilhermeblanco's sign-off. |
Ocramius
added a commit
that referenced
this pull request
Jan 13, 2015
…fallback Class metadata loading fallback hook
This was referenced Dec 6, 2015
This file contains hidden or 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
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.
Enables loading class metadata when loading failed (in subclasses).
See doctrine/orm#385
Note that I preferred inheritance to avoid having an
EventManagerin here, though it may be a perfectly acceptable dependency in this case, therefore it is up for discussion.