I created a PR a while ago for that issue (reported by another user)
It looks like I will need to update it to match the core change, though. Hopefully, once it is fixed, it will get some attention.