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

Merge release 1.3.6 into 2.0.x #2151

Merged
merged 2 commits into from
Jan 13, 2020

Conversation

doctrinebot
Copy link

Release 1.3.6

1.3.6

  • Total issues resolved: 1
  • Total pull requests resolved: 3
  • Total contributors: 3

Documentation

BC Break,Bug

Bug

AntoniusGolly and others added 2 commits December 26, 2019 13:52
Before I work on this PR I would like to ask on your opinion. I find the way the subscriber is written misleading. Currently, the subsriber will try to link the ODM Document to *every* ORM Entity. With other words the subscriber is  called post load of *every* entity defined in the project. What we want is something like

```
public function postLoad(LifecycleEventArgs $eventArgs)
    {
        $entity = $eventArgs->getEntity();

        if ($entity instanceof Order) {
            // business here
        }
}
```

Am I correct or am I missing a piece of information?

Also, in this PR I would add an example of a .yaml configuration of the listener.
@malarzm
Copy link
Member

malarzm commented Jan 13, 2020

I'm done clicking rebuild on travis, test failure is unrelated as I'm merging docs changes

@malarzm malarzm merged commit 608d94f into 2.0.x Jan 13, 2020
@malarzm malarzm deleted the 1.3.x-merge-up-into-2.0.x_5e1cb820449e20.98695361 branch January 13, 2020 18:53
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.

3 participants