Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation adjustments #5
Documentation adjustments #5
Changes from 1 commit
fe76afb
6dc43f4
4b4ecf7
ad6923e
68d5ba8
aac9db2
69d0fad
171f137
47d5303
b2633db
42f8b9a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might need to hold off on this one until 0.4 when I have full set of tests + bug fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have removed this coverage shield for now until I get the source code tested to standards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may need to be amended. See also next comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and removed
typos
from the linter. It found one typo and one false positive. I fixed those, and it is now failing in CI and giving no indication why (I can't reproduce locally)I feel fairly strongly that typos gets in the way more than it helps (Ive had trouble getting dictionaries to be read and trouble getting CI to tell me what happened with
typos
). Unless you feel strongly about this, I may leave it out of the linterThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It surprises me, that
typos
caused this trouble. Here are some notes:typos
appears to never have been declared as a dependency (smth I overlooked as well) which makes me wonder why trying to execute the command gave an exit code2
rather than127
, but could be the reason why it kept failing at the endtypos
does NOT use a dictionary by design. Instead, it keeps an internal list of common typos which it detects and marks. This cuts down a LOT on false positives compared to e.g. pylint's spell checker. See here for more details.