Hello, thank you for your feedback. The issue is now fixed and it will be applied for version 0.3.2 which should be released during this week.
