September 6-19, 2020 in Darker: Refining revision handling and addressing user feedback #630
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 period saw our community focusing on refining Darker's handling of Git revisions and addressing user feedback, particularly regarding the
--revision
option. We made progress in clarifying how Darker interacts with Git repositories and discussed potential improvements to enhance its functionality for different use cases.A significant discussion centered around issue #64, where we clarified the behavior of the
--revision
argument. We explained how Darker processes files and directories, emphasizing that it only reformats files modified since the specified revision. This conversation highlighted the need for better documentation and possibly some adjustments to make Darker's behavior more intuitive for users transitioning from other tools like Black.We also tackled a more complex issue (#79) regarding how Darker handles comparisons between branches, especially when dealing with uncommitted changes. The community explored various options to improve the
--revision
functionality, considering scenarios where users might want to compare against the working tree or the latest common ancestor of branches. This discussion showcased our commitment to making Darker more versatile while maintaining its ease of use.As we continue to refine Darker, we're balancing the need for powerful features with the desire to keep the tool intuitive and aligned with Git conventions. The active engagement from our community members in these technical discussions is invaluable, helping us shape Darker to better meet the needs of its users while maintaining its core simplicity and efficiency.
Beta Was this translation helpful? Give feedback.
All reactions