Awesome point. I'm afraid addressing the issue will fall outside the scope of v1 but I've already added it to my list of functionality to examine for the next build. Thanks!