Alright, this was just fixed in a recently merged pull request. Thanks for your input!