Hi @Barod,
the workaround is not required anymore with v4.3.1. We have added a new option, see here.
Best, Simon