List view

• Stability

  There are some stability issues in Darglint which could be resolved with more careful testing. This stability milestone will cover the following: - Fuzz testing with the python grammar and docstring grammar, * This doesn't have to be AFL or continuous fuzzing or anything like that. A naive implementation would probably work perfectly fine. - Test/re-test comparison for repositories, * To ensure that order is maintained. Ideally, runs of darglint would always be exactly the same. - Write pre-commit hooks that check that pre-commit tests were run, - Run pre-commit tests on Travis CI.

  No due date
  0% complete0 open0 closed

• Logging

  Darglint should have configurable logging. All asserts should be converted to a custom assert function which logs the error, and (depending on the config), throws an exception.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• AutoFormatter

  No due date

  •0/1 issues closed
  0% complete1 open0 closed