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

Depend directly on the symfony stopwatch component #934

Merged
merged 1 commit into from
Mar 3, 2020

Conversation

goetas
Copy link
Member

@goetas goetas commented Mar 2, 2020

Before this commit doctrine/migrations was using a wrapper on the symfony stopwatch component, but that wrapper was still returning the original symfony stopwatch event objects, making the wrapping almost useless as the doctrine code was still relying on the doctrine implementation. This commit just removes the wrapper and depends directly on the symfony stopwatch component.

Q A
Type
BC Break
Fixed issues

Summary

Before this commit doctrine/migrations was using a wrapper on the symfony stopwatch component, but that wrapper was still returning the original symfony stopwatch event objects, making the wrapping almost useless as the doctrine code was still relying on the doctrine implementation. This commit just removes the wrapper and depends directly on the symfony stopwatch component.
@goetas goetas merged commit b073e2c into doctrine:master Mar 3, 2020
@goetas goetas deleted the use-symfony-stopwatch branch March 3, 2020 13:46
@goetas goetas added this to the 3.0.0 milestone Mar 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants