@girish This is fixed in 1.4.2. Thanks!
This is fixed in the latest package (1.3.0)
@nj Thanks for reporting, I have fixed this in the latest package.
In case anyone else has this question it is this format