July 28 - August 4, 2024 in Darker: VSCode integration fixes and exit code refinements

[akaihola]

This week, we made progress on addressing VSCode integration issues and refining our exit codes. We identified the root cause of the VSCode integration problem, where Darker was incorrectly handling line endings when used with the Black formatter extension. The issue stems from our line ending detection function in darkgraylib, which sometimes results in double line breaks. We're now working on a fix to ensure consistent line ending behavior across different environments (Issue #604, PR #605).

We've refined our exit codes to provide more specific information about different error scenarios (PR #595). Now, we use distinct codes for file not found (2), invalid arguments (3), missing dependencies (4), and unknown failures (123). This aligns better with other tools like Black and improves error handling in CI/CD pipelines. We're also considering a unique exit code (21) for the GitHub action when the specified working-directory doesn't exist (Issue #594).

In other developments, we've added support for Black's --preview flag via Darker's CLI and configuration files (PR #589). We're exploring the possibility of supporting ruff format as an alternative formatter (Issue #521), which could potentially offer performance improvements. Lastly, we fixed a CI compatibility issue with Pip >= 24.1 (PR #597) and updated our documentation to include py313 in the --target-version choices (PR #596), keeping in sync with Black's updates.

---

{
    "end_date": "2024-08-03",
    "llm": "openrouter/anthropic/claude-3.5-sonnet:beta",
    "powered_by": "https://github.com/akaihola/repo-summary-post/tree/v0.0.3",
    "start_date": "2024-07-28"
}

[akaihola]

Ruff and uv are on my mind these days, so I guess #521 (ruff format support) and migrating to uv in GitHub actions could be next on the feature list.