Hello! Thanks again for reporting the issue, and we've just fixed this issue in our code base! The fix is available right now for premium subscription users, and will be publicly available in our next release!

Now it will work like the initial sample you pointed, without the need of any custom config blocks!