Yeah, someone commented on that issue, it was fixed but i guess it just came back? I'll make sure to fix it on v0.4.
