@User if you wouldn't mind opening up a github issue for this, we will fix it for our next release.