Hi, thank you for reporting this. It is a known issue and it has been fixed and will be released in the next update (2.0.0).
Great, thank you!