You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have quite a few typos/misspellings in MSS. We could introduce a spellchecker as an additional linter. codespell is one that I am aware of. This is what it finds on the current develop branch:
In py scripts it better would checks only comments or doc strings.
Also in the conf file it would create a problem
There it catches a different problem in data or source. These are only available with docs builded. But it likly should be height ./docs/gallery/code/downloads/Top_PVTropo01.py:70: hight ==> height, high
So it is useful, but we should not trust it on everything.
Of course there are some false positives. Fixing misspellings we already have must be done in a way that it does not break anything (and if not possible we can have excludes for specific cases).
In py scripts it better would checks only comments or doc strings.
In general I think that is a good thing. Function, method and variable names should also be checked for typos and for new code there is no issue with that at all. As said above, we probably cannot fix everything we already have, but what can be fixed should be, in my opinion.
So it is useful, but we should not trust it on everything.
I am not suggesting just letting it auto-fix stuff. I am suggesting another linter workflow, like flake8, that would need to be green to merge stuff.
We have quite a few typos/misspellings in MSS. We could introduce a spellchecker as an additional linter. codespell is one that I am aware of. This is what it finds on the current develop branch:
Some of these are certainly false-positives, but many aren't.
The text was updated successfully, but these errors were encountered: