Great catch! This should be fixed in version 0.1.1. Could you confirm if upgrading resolves the issue for you?
1 Like
Great catch! This should be fixed in version 0.1.1. Could you confirm if upgrading resolves the issue for you?