Document force_union_syntax and force_uppercase_builtins
#16048
Conversation
sobolevn
force-pushed
the
document-force-options
branch
from
eb5d0d7 to
b3e3f56
Compare
docs/source/config_file.rst
Outdated
| .. confval:: force_lowercase_builtins | ||
|
|
||
| :type: boolean | ||
| :default: False | ||
|
|
||
| Force to use ``List`` instead of ``list`` . |
There was a problem hiding this comment.
Same comment as with force_union_syntax -- it looks like this option just impacts whether or not the messages mypy displays to the user use PEP-585 syntax. Also: the config option is force_uppercase_builtins, not force_lowercase_builtins
There was a problem hiding this comment.
Yes, this is just about messages. This is why I put these two in "Configuring error messages" category. Is there any better way to describe them?
There was a problem hiding this comment.
This is why I put these two in "Configuring error messages" category.
Ah, I didn't spot that, sorry!
Is there any better way to describe them?
I think "in error messages" is a useful qualifier -- have made some suggestions in review comments 👍
Co-authored-by: Alex Waygood <[email protected]>
sobolevn
changed the title
force_union_syntax and force_lowercase_builtinsforce_union_syntax and force_uppercase_builtins
|
Should we also document these as command-line options? It looks like |
Users don't know about them: typeddjango/pytest-mypy-plugins#126
Since they are quite important for testing, I think that it is a must to include them.