@JHSinclair thanks for reporting this! This should now be fixed in our latest release (v0.1.3) – let us know if you still see any bad behaviour.
@JHSinclair thanks for reporting this! This should now be fixed in our latest release (v0.1.3) – let us know if you still see any bad behaviour.