January 2022 in Darker: VSCode Integration Improvements and Linter Flag Challenges #669
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
-
This month, we focused on enhancing Darker's integration with VSCode and addressing configuration challenges. A community member reported issues with VSCode integration when using the
-L
/--lint
flag (#252). The problem was resolved by adding quotes around the linting tool or its path in the VSCode configuration. However, it was noted that there isn't full integration between chosen linting tools (like flake8 or mypy) and Darker when running within VSCode, despite these tools working well independently.We also made progress on the previously reported issue of tmp files being filtered out before checking for matching tracked files (#249). A potential solution was proposed, involving a small change to the
should_reformat_file
function. This modification checks the suffix of the original file rather than the temporary file, potentially improving compatibility with VSCode's "format on save" functionality. This update could have broader implications for Darker's interaction with IDEs that use similar temporary file mechanisms for formatting.Beta Was this translation helpful? Give feedback.
All reactions