Bharath Natarajan

@david-shiko @Noitham thanks for your patience here. We will plan to address this in our next major release. We are tentatively planning to begin work on this by mid December.

thanks for sharing a workaround, @mrbrentkelly! We are planning to address this issue along with other improvements in the next major release coming up this quarter. I'll share exact timelines...

We are planning to address this issue along with other improvements in the next major release coming up this quarter. I'll share exact timelines by the mid of June.

@mikehuebner Apologies for not communicating timelines earlier. v4 beta is already out and it should address this issue. Could you confirm if this is resolved?