March 24-31, 2024 in Darker: VSCode compatibility and project maintenance #724
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 week saw improvements in Darker's compatibility with VSCode and various project maintenance tasks. We merged a fix to allow the
--stdout
option to work with stdin input, addressing an issue that was affecting VSCode users (PR #574). This change makes it easier to configure Darker with the VSCode black-formatter extension. We also updated our README with improved instructions for VSCode integration and clarified the "How does it work?" section, adding information about Darker's limitations and potential work-arounds (PR #566).On the project maintenance front, we moved the
update-contributors
script to a separate development tools package (PR #577), addressing a long-standing issue with missing dependencies. We also fixed README badge links (PR #576) and made improvements to package data inclusion, allowing Mypy to understand typing during editable installs (PR #575). The community continued discussions on potential performance improvements, with a new issue opened to add a summary of time spent in different phases of a Darker run for debugging purposes (Issue #573). Additionally, we began the process of deprecatingskip_*
Black options in the[tool.darker]
configuration section (PR #578), paving the way for future updates to our configuration handling.Beta Was this translation helpful? Give feedback.
All reactions