Spring update: 1.7.0 and 1.7.1 released, working on moving linting into a separate tool #484
akaihola
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Darker development has been progressing in short spurts during my freetime and with occasional contributions from the community. Needless to say, it's always great to receive suggestions, bug reports as well as documentation and code pull requests. Thank you for the collaboration on those!
1.7.0 feature release
For the 1.7.0 feature release, highlights from resolved issues and merged pull requests are:
rev1
, then atrev2
, then only show changed and new linter message. This fixes the old flawed approach which just limited shown linter messages to those on modified lines. See discussion Holiday season, 1.6.1 released and working towards 1.7.0 #451 for details on baseline linting.--stdin-filename=PATH
-f
/--flynt
option for converting old-style format strings to f-strings (using Flynt)--target-version=
/-t
command line option now passed to Black; also thetarget-version =
configuration option is honoredBug reports and feature requests were submitted by @qubitd, @jedie, @aljazerzen and @tgross35. Reviewer champions were @simonf-dev and @jedie. Warm thanks to you all!
1.7.1 bugfix release
In the 1.7.1 feature release the issue resolutions and pull request merges included:
git worktree
to create a repository checkout for baseline linting. This avoids issues with the previousgit clone
andgit checkout
based approach.Next up
@okuuva submitted the well-founded idea of moving the linting feature (
--lint
/-L
option) to a separate tool. We discussed the rationale and details in #304, and the work is being done in #465, the new Graylint repository, and the Darkgraylib repository which holds common code between the two tools. At some point in the future, probably in version 2.0.0, #466 will remove linting support form Draker, but until then it will continue to work.As always, help in reviewing, discussing, coding and documenting is highly appreciated. Pick a PR to work on and drop a note in its comments!
Beta Was this translation helpful? Give feedback.
All reactions