Thank you for submitting this, I hadn't noticed it myself. It was caused by a small refactor I did in a recent update, but it's fixed now.