Thanks for the follow-up, Julien, and for bringing this up again. We do still have this on the radar – as I noted in the other thread, this is slated for inclusion in 2.1. That build is still in the works so while this code has been added in our development environment, 2.1 is not yet ready for prime time so we haven’t released it to the public.
We’re focusing mostly on bug fixes and heavily-needed features for the dot releases (ie 2.0.8), and doing features on a more broad sense in 2.1. Don’t worry, though…this one hasn’t slipped through the cracks. 2.1 should be out sometime later in the summer and will have this fix you’ve requested in it. We appreciate your patience so far.