1 reply

Fixed in v0.22. Thanks for the report!