Skip to content
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

fix(checks): make am_pm check case sensitive #620

Merged
merged 1 commit into from Jul 11, 2021

Conversation

chreekat
Copy link
Contributor

Upon using proselint on an email, I immediately noticed that "lowercase am/pm" was not checking that am/pm was actually lower case.

I attempted to fix that here (and throw in some tests). But, I'm not a python hacker, and I have no idea what the usual workflows are for python projects. I did run nosetests within the tests directory, but my new test still fails. Is there some build step I'm missing? Or is my test broken?

P.S. It would be great if you could throw a few words into the contributing guide about how to approach the project as an absolute Python beginner. E.g. is pip install --user --upgrade . the right way to install a modified version? Or, how do I run it without even installing it locally? :)

@chreekat chreekat closed this Sep 23, 2016
@chreekat chreekat deleted the actually-lower-case branch September 23, 2016 10:56
@chreekat chreekat restored the actually-lower-case branch September 23, 2016 11:01
@chreekat chreekat reopened this Sep 23, 2016
@chreekat
Copy link
Contributor Author

Sorry for the close/reopen; I momentarily wanted nothing to do with this project after getting shit on in one of the issue threads.

@Nytelife26 Nytelife26 added the status: awaiting-triage Issues and PRs awaiting investigation and relabelling. label May 29, 2021
@Nytelife26 Nytelife26 added bug: confirmed Bugs that were confirmed in triage. cat: false-positive Issues and PRs related to false positives in proselint rules. priority: low Issues and PRs that should be resolved, but can be postponed. status: wip Issues and PRs that are still a work in progress. type: fix Issues and PRs related to bugs. version: patch Issues and PRs with bug fixes belonging to the next patch release. and removed status: awaiting-triage Issues and PRs awaiting investigation and relabelling. labels Jul 10, 2021
@Nytelife26 Nytelife26 mentioned this pull request Jul 11, 2021
@codecov
Copy link

codecov bot commented Jul 11, 2021

Codecov Report

Merging #620 (b2d1d26) into main (53076b2) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #620   +/-   ##
=======================================
  Coverage   94.34%   94.34%           
=======================================
  Files          82       82           
  Lines        1131     1131           
=======================================
  Hits         1067     1067           
  Misses         64       64           
Flag Coverage Δ
macos-latest 94.34% <100.00%> (ø)
py3.6 93.74% <100.00%> (ø)
py3.7 93.74% <100.00%> (ø)
py3.8 94.34% <100.00%> (ø)
py3.9 94.34% <100.00%> (ø)
pypypy3 93.74% <100.00%> (ø)
ubuntu-latest 94.34% <100.00%> (ø)
windows-latest 94.34% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
proselint/checks/dates_times/am_pm.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53076b2...b2d1d26. Read the comment docs.

@Nytelife26 Nytelife26 changed the title WIP: Actually lower case am/pm make am_pm check case sensitive Jul 11, 2021
@Nytelife26
Copy link
Collaborator

Good fix, thanks for the PR - and I'm sorry for whatever happened in that issue all that time ago.

@Nytelife26 Nytelife26 changed the title make am_pm check case sensitive fix(checks): make am_pm check case sensitive Jul 11, 2021
@Nytelife26 Nytelife26 merged commit 50d2a48 into amperser:main Jul 11, 2021
@Nytelife26 Nytelife26 added bug: fixed-in-next Bugs present in the current release but fixed on the main branch. and removed bug: confirmed Bugs that were confirmed in triage. labels Jul 11, 2021
@Nytelife26 Nytelife26 removed the status: wip Issues and PRs that are still a work in progress. label Jul 11, 2021
@Nytelife26 Nytelife26 added the status: merge-ready PRs that are ready to merge. label Jul 11, 2021
@Nytelife26 Nytelife26 added bug: fixed Bugs that have been fixed. and removed bug: fixed-in-next Bugs present in the current release but fixed on the main branch. labels Aug 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: fixed Bugs that have been fixed. cat: false-positive Issues and PRs related to false positives in proselint rules. priority: low Issues and PRs that should be resolved, but can be postponed. status: merge-ready PRs that are ready to merge. type: fix Issues and PRs related to bugs. version: patch Issues and PRs with bug fixes belonging to the next patch release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dates_times.am_pm.lowercase_periods is triggered when using uppercase letters
2 participants