Skip to content

Releases: amperser/proselint

0.3.1

05 Sep 15:03
Compare
Choose a tag to compare

0.3.0

30 Sep 18:46
Compare
Choose a tag to compare

Full Changelog

Merged pull requests:

0.2.1

05 Sep 15:03
Compare
Choose a tag to compare

Full Changelog

Implemented enhancements:

  • Create a timing test on the command line #191

Merged pull requests:

0.2.0

18 Sep 04:48
Compare
Choose a tag to compare

Full Changelog

Closed issues:

  • should we delete the python3 branch now that it's complete? #157
  • Add Louis C.K.'s rule on "the N-word" #154
  • Upgrade to most recent version of dependencies #144
  • Figure out the right name for a "check" #21
  • Extract rules from DFW's dictionary in The Telegraph #4

Merged pull requests:

0.1.0

05 Sep 15:03
Compare
Choose a tag to compare

Implemented enhancements:

  • Move cache to a place where Heroku can see it #90
  • Fork NLTK / TextBlob and speed up importing them #88

Fixed bugs:

  • "every possible" flagged as comparing an uncomparable #129
  • Make proselint work in normal install mode #91
  • Decade detector false alarms on 50 cent posessive #82
  • Fix web plugin's handling of Unicode #62

Closed issues:

  • Extract business euphemisms from Inc article #136
  • Refactor proselint/checks/norris/denizen_labels.py from a D on Code Climate #127
  • Refactor proselint/checks/garner/sexism.py from a D on Code Climate #126
  • Refactor proselint/checks/butterick/symbols.py from a D on Code Climate #125
  • Test ticket from Code Climate #124
  • Create a linter email service #123
  • Make a splash page to collect email addresses #102
  • Get a logo #101
  • Add rate limiting to API #100
  • Use worker and web processes #96
  • Issue with broken link parsing #84
  • Extract rules from "Anguished English" #67
  • Make pep8 and pep257 run cleanly #61
  • Add rule about spelling names correctly #58
  • Build online writing editor using http://codemirror.net/? #50
  • Check out the cement framework for command line utilities #47
  • False alarms, corpora, QA, and contributing back #45
  • Create a .proselintrc file #39
  • Create plugin for Sublime Text #35
  • Create an API #33
  • Using "a" vs. "an" #31
  • Figure out test inheritance #30
  • Great writing should come back nearly clean #25
  • Don't lint quoted text #24
  • Architecture for sharing processed data across rules #20
  • It's et al., not et. al #18
  • Sort errors by the position in which they occur #12
  • Integrate into Sublime Text as a linter #11
  • Extract rules from write-good #5
  • working out how i can best contribute using github/git #3
  • Create a plugin system #2
  • Choose a sensible naming/numbering scheme for errors #1

Merged pull requests: