NOTE: This is NOT an issue, that breaks our implementation anymore. This ticket is more created to talk about this topic as mentioned here as well: #913 (comment) The behaviour change in v0.19.0 fo...