August 30 - September 5, 2020 in Darker: Configuration Files Take Shape and Community Engagement Grows #629
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 significant progress in Darker's development, with a focus on refining configuration options and addressing user-reported issues. We made strides in implementing configuration files, a feature that will greatly enhance Darker's usability and flexibility.
The discussion on configuration files (#49) reached a consensus, with the community agreeing to use
pyproject.toml
with a[tool.darker]
section. This decision aligns Darker with industry standards set by Black and isort, allowing users to easily set default options for their projects. The proposed format includes options for source directories, revision, diff output, isort integration, and linting tools. This development will streamline Darker's usage across different environments and projects.We also addressed several user-reported issues, demonstrating our commitment to improving Darker's functionality. A problem with parsing files beginning with specific pylint comments was identified (#63), highlighting our ongoing efforts to enhance compatibility with various coding styles. We clarified the usage of the
-r
/--revision
argument in response to a suggestion for selecting all file changes since a revision (#64). This discussion underscored the power of Darker's existing features while also revealing areas where we can improve our documentation to better guide users.As we continue to refine Darker, we're balancing feature additions with maintaining our project's simplicity and efficiency. The active engagement from our community in discussions and problem-solving is driving Darker's evolution, ensuring it remains a valuable tool for code formatting.
Beta Was this translation helpful? Give feedback.
All reactions