Darker

Latest version: v2.1.1

Safety actively analyzes 675402 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

1.2.3

===================

Added
-----
- A unified ``TextDocument`` class to represent source code file contents
- Move help texts into the separate ``darker.help`` module
- If AST differs with zero context lines, search for the lowest successful number of
context lines using a binary search to improve performance
- Return an exit value of 1 also if there are failures from any of the linters on
modified lines
- Run GitHub Actions for the test build also on Windows and macOS

Fixed
-----
- Compatibility with Mypy_ 0.812
- Keep newline character sequence and text encoding intact when modifying files
- Installation now works on Windows
- Improve compatibility with pre-commit. Fallback to compare against HEAD if
``--revision :PRE-COMMIT:`` is set, but ``PRE_COMMIT_FROM_REF`` or
``PRE_COMMIT_TO_REF`` are not set.

1.2.2

===================

Added
-----
- Get revision range from pre-commit_'s ``PRE_COMMIT_FROM_REF`` and
``PRE_COMMIT_TO_REF`` environment variables when using the ``--revision :PRE-COMMIT:``
option
- Configure a pre-commit hook for Darker itself
- Add a Darker package to conda-forge_.

Fixed
-----
- ``<commit>...`` now compares always correctly to the latest common ancestor
- Migrate from Travis CI to GitHub Actions

1.2.1

===================

Added
-----
- Travis CI now runs Pylint_ on modified lines via pytest-darker_
- Darker can now be used as a pre-commit hook (see pre-commit_)
- Document integration with Vim
- Thank all contributors right in the ``README``
- ``RevisionRange`` class and Git repository test fixture improvements in preparation
for a larger refactoring coming in `80`_

Fixed
-----
- Improve example in ``README`` and clarify that path argument can also be a directory

1.2.0

===================

Added
-----
- Configuration for Darker can now be done in ``pyproject.toml``.
- The formatting of the Darker code base itself is now checked using Darker itself and
pytest-darker_. Currently the formatting is a mix of `Black 19.10`_ and `Black 20.8`_
rules, and Travis CI only requires Black 20.8 formatting for lines modified in merge
requests. In a way, Darker is now eating its own dogfood.
- Support commit ranges for ``-r``/``--revision``. Useful for comparing to the best
common ancestor, e.g. ``master...``.
- Configure Flake8_ verification for Darker's own source code

1.1.0

===================

Added
-----
- ``-L``/``--lint`` option for running a linter for modified lines.
- ``--check`` returns ``1`` from the process but leaves files untouched if any file
would require reformatting
- Untracked Python files – e.g. those added recently – are now also reformatted
- ``-r <rev>`` / ``--revision <rev>`` can be used to specify the Git revision to compare
against when finding out modified lines. Defaults to ``HEAD`` as before.
- ``--no-skip-string-normalization`` flag to override
``skip_string_normalization = true`` from a configuration file
- The ``--diff`` and ``--lint`` options will highlight syntax on screen if the
pygments_ package is available.

Fixed
-----
- Paths from ``--diff`` are now relative to current working directory, similar to output
from ``black --diff``, and blank lines after the lines markers (`` ... ``) have
been removed.

1.0.0

===================

Added
-----
- Support for Black_ config
- Support for ``-l``/``--line-length`` and ``-S``/``--skip-string-normalization``
- ``--diff`` outputs a diff for each file on standard output
- Require ``isort`` >= 5.0.1 and be compatible with it
- Allow to configure ``isort`` through ``pyproject.toml``

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.