Just fixed this, should be in the next release (in a day or two).
It's fixed in version 1.0.0 Beta 7o. Thank you.