October 2 - November 12, 2023 in Darker: Addressing CI issues and enhancing VSCode compatibility #716
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
Uh oh!
There was an error while loading. Please reload this page.
-
This period saw us tackling various challenges related to continuous integration and editor integration. We addressed a GitLab CI issue where Darker was failing due to "dubious ownership" in the repository (Issue #524). This problem persisted even after marking the directory as safe for Git, highlighting a potential area for improvement in our handling of Git configurations in CI environments.
We also made progress on enhancing VSCode compatibility. A bug was identified where the
--stdout
option threw an error when a dash was given to indicate stdin input, breaking VSCode integration (Issue #523). This led to discussions about potential fixes and workarounds for users trying to use Darker with the new VSCode Black formatter extension. Additionally, we merged a fix for the pre-commit hook configuration (PR #519), ensuring that each argument is on its own line to prevent misinterpretation. On the documentation front, we corrected a typo in the pylint example in our README (PR #520). Lastly, we began exploring the possibility of supportingruff format
as an alternative formatter (Issue #521), which could potentially offer performance improvements in the future.Beta Was this translation helpful? Give feedback.
All reactions