Niels Keurentjes

Your suggested code seems perfectly reasonable. If we can reduce a common semi-custom end-user requirement to a single line of code I think that's the optimal solution by definition.

Some food for thought: http://fabien.potencier.org/pragmatism-over-theory-protected-vs-private.html Fabien makes some good points about `protected` methods also implicitly being part of the public API of a project. It's more pronounced in a project...

That was my main intent with giving the food for thought: you are both working towards a new major version and documenting the API. That is the best time, if...

This is not possible in the "driver" as the hardware does not support it, nor should it. Faking this data should be a part of the application test suite, you...

> Supporting the Order enum directly is a feature I don't see for ORM 2.x anymore, tbh. ...thus forcing a double migration on all of us, migrating to `Order::Ascending->value` first...

Preferably the constants would remain gone in 3 as you're otherwise going to be stuck with them sort of forever. I would just like a better migration path than we...

> The "migration path" that you're discussing is actually a workaround for people that have used those constants in an undocumented way, outside of their scope. Fair enough, I forgot...

My use case is quite specific, I have a bunch of nested objects which can all be selected (leaves and nodes). Given a simple tree like this: ``` Root #1...

That would be awesome :) It was just a suggestion because it seems you've already done all the hard work on showing a tree, splitting it out to have the...

Thanks for the kind words 💯 Rate limiting is most certainly one to be put on the list. I'm also considering wrapping up Recaptcha, [Akismet](https://github.com/omines/akismet) and maybe even the classic...