feat(metadata): add support for stateOptions in YAML and XML for Doctrine ORM/ODM #7217
Conversation
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
|
could you please rebase I want to merge this thanks! Also I'd say that this is a bug fix it should target 4.1 |
fmata
force-pushed
the
feature/stateoptions-config
branch
from
4510664 to
50db582
Compare
|
@soyuka rebased & target branch changed. |
|
thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I recently discovered stateOptions parameter (#7211 (comment)) but it's impossible to use it with YAML or XML to configure Doctrine entity/document class.
It doesn't resolve my linked issue but at least now it's possible to configure stateOptions more easily :)