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

make Base LifecycleEventArgs usable in orm and odm #222

Merged
merged 4 commits into from Dec 5, 2012
Merged

make Base LifecycleEventArgs usable in orm and odm #222

merged 4 commits into from Dec 5, 2012

Conversation

docteurklein
Copy link
Contributor

Pull requests are to come for both orm and odm to make use of this.

The main goal is to make more abstract listeners, compatible with both orm and odm.

@doctrinebot
Copy link

Hello,

thank you for positing this Pull Request. I have automatically opened an issue on our Jira Bug Tracker for you with the details of this Pull-Request. See the Link:

http://doctrine-project.org/jira/browse/DCOM-142


/**
* @var object
*/
private $entity;
protected $object;
Copy link
Member

Choose a reason for hiding this comment

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

why changing the visibility ? You have getter for them, and child classes are not meant to replace them either

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right.

beberlei added a commit that referenced this pull request Dec 5, 2012
make Base LifecycleEventArgs usable in orm and odm
@beberlei beberlei merged commit d514e39 into doctrine:master Dec 5, 2012
@jmikola
Copy link
Member

jmikola commented Dec 19, 2012

@beberlei: Will this be in the 2.3.1 release? And if so, any ETA on when that might be?

@stof
Copy link
Member

stof commented Dec 19, 2012

@jmikola This is only in master AFAIK, so it is probably for 2.4

@jmikola
Copy link
Member

jmikola commented Dec 19, 2012

Ah, I didn't realize there was a separate 2.3 branch already. Makes sense, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants