-
Notifications
You must be signed in to change notification settings - Fork 6
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
Improve CycleOrmBootloader bindings #33
Improve CycleOrmBootloader bindings #33
Conversation
Codecov ReportBase: 67.84% // Head: 69.17% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #33 +/- ##
============================================
+ Coverage 67.84% 69.17% +1.33%
- Complexity 435 436 +1
============================================
Files 52 52
Lines 1132 1275 +143
============================================
+ Hits 768 882 +114
- Misses 364 393 +29
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@kafkiansky Hi! Sorry for long response. Could you fix error with static analysis? |
@butschster, Hi. I fixed it. |
Thank you! You are the best! |
Can you add the second test please with EM mock?
|
Made the
EntityManagerInterface
a singleton, so that thepersist
andrun
operations could be called independently of each other and the operations on the entity were performed. Also, instead of clearing the heap withORMInterface
, did it using theEntityManagerInterface::clean
method.But I find it a bit strange that the
EntityManager
has an argument$cleanHeap
in theclean
method that is not in theEntityManagerInterface
. IMHO, it should not be inEntityManager
at all, so both heap and entity manager should be called in the finalizer as follows:And
EntityManager
should only create a new UnitOfWork instance: