GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Chaining for EM methods persist()/flush(), to write more elegant code $em->persist($account)->flush();
chaining for EM methods persist/flush;
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:
Why only these two and not also other methods (beginTransaction, rollback, commit, clear, close, remove, detach, copy, lock and initializeObject)?
I think this has already been rejected at least 10 times since the release of Doctrine 2.0
This was already refused before. Doctrine generally discourages usage of fluid interfaces where they are not used to build domain specific languages, like the query builder. The idea of saving few keystrokes is not sufficient to introduce a fluid interface.