hugoattal opened this issue 3 years ago · 0 comments
This bug was introduced by 3.0. It's fixed and ready to deploy.