This should have been fixed in version 1.1.0 but I'll take another look and push an update if I can replicate the issue.
