Open andre-senna opened 1 week ago
@andre-senna
I suppose this issue was already fixed in one of the previous updates. I couldn´t reproduce this error.
Recent fixes wouldn't affect the behavior of a previous (0.4.4) version.