Consider using true/false for all booleans in docs
kristianheljas opened this issue · 3 comments
Based on the community decision to use true/false for boolean values in documentation and examples, we ask that you evaluate booleans in this collection and consider changing any that do not use true/false (lowercase).
See documentation block format for more info (specifically, option defaults).
If you have already implemented this or decide not to, feel free to close this issue.
P.S. This is auto-generated issue, please raise any concerns here
I will migrate to true/false instead of yes/no but it will take some time. This issue will be kept open until they're all resolved.
Yeah, in the next 2 weekends I will have some time so I am going to finish the task with the warnings!
In the #361, we have changes from yes/no to true/false. But you have right to still open that issue until we resolve it.
He's also referring to the documentation itself in each module. That'll need to be updated.