You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This week saw improvements in Darker's configuration handling and continued discussions on various issues. We merged a fix to correctly display the configuration section name when using the -vv option (PR #586). This change ensures that the output now shows [tool.darker] instead of [tool.darkgraylib], providing a more accurate representation of Darker's configuration.
We also revisited some older issues, including a potential problem with pre-commit hooks returning non-zero exit codes even when there are no linting errors (Issue #390). The community is investigating whether recent changes in Graylint, which Darker now uses for linting support, might have resolved this issue. Ongoing discussions include exploring the use of Black's --preview option for early warnings about style changes (Issue #457) and improving documentation with Git diagrams to illustrate the --revision argument variations (Issue #326). We're also considering the use of Dependabot for updating dependencies and GitHub Action versions (Issue #341) to streamline our maintenance process.
Another open issue being addressed is Darker's handling of blank lines re-inserted by Black where a user had only deleted lines (Issue #371). This highlights the complex interactions between Darker and Black's formatting choices, and we're working on developing a minimal test case and a fix for this behavior.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This week saw improvements in Darker's configuration handling and continued discussions on various issues. We merged a fix to correctly display the configuration section name when using the
-vv
option (PR #586). This change ensures that the output now shows[tool.darker]
instead of[tool.darkgraylib]
, providing a more accurate representation of Darker's configuration.We also revisited some older issues, including a potential problem with pre-commit hooks returning non-zero exit codes even when there are no linting errors (Issue #390). The community is investigating whether recent changes in Graylint, which Darker now uses for linting support, might have resolved this issue. Ongoing discussions include exploring the use of Black's
--preview
option for early warnings about style changes (Issue #457) and improving documentation with Git diagrams to illustrate the--revision
argument variations (Issue #326). We're also considering the use of Dependabot for updating dependencies and GitHub Action versions (Issue #341) to streamline our maintenance process.Another open issue being addressed is Darker's handling of blank lines re-inserted by Black where a user had only deleted lines (Issue #371). This highlights the complex interactions between Darker and Black's formatting choices, and we're working on developing a minimal test case and a fix for this behavior.
Beta Was this translation helpful? Give feedback.
All reactions