Positional boolean parameters are a bad practice because they are very ambiguous. Using named boolean parameters is much more readable because it inherently describes what the boolean value represents.
@dernoun You are right. But at this point this would be a massive breaking change. Everyone using this lib would have to fix it, so I have decided not to do it. Thanks for the good idea, anyway.
This is best practices from the official documentation.
AVOID positional boolean parameters.
Positional boolean parameters are a bad practice because they are very ambiguous. Using named boolean parameters is much more readable because it inherently describes what the boolean value represents.