This is fixed now in v2.0.
↧
This is fixed now in v2.0.