X-diff-cover

Latest version: v1.0.0

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

Scan your dependencies

Page 8 of 19

2.4.0

* Drop support for python 3.4 and upgrade syntax with pyupgrade. Thanks hugovk
* Add support for cppcheck. Thanks noahp

2.3.0

* Add PMD xml driver Thanks bit-ranger (https://github.com/Bachmann1234/diff_cover/pull/117)

2.2.0

* Add --version flag to both commands. Shocked we never had this

2.1.0

* New option that controls how the patch is obtained: `--diff-range-notation`, defaulting to `...`.

Traditionally in git-cover the symmetric difference (three-dot, "A...M") notation has been used: it includes
commits reachable from A and M from their merge-base, but not both, taking history in account. This includes cherry-picks
between A and M, which are harmless and do not produce changes, but might give inaccurate coverage false-negatives.

Two-dot range notation ("A..M") compares the tips of both trees and produces a diff. This more
accurately describes the actual patch that will be applied by merging A into M, even if commits have been
cherry-picked between branches. This will produce a more accurate diff for coverage comparison when complex
merges and cherry-picks are involved. Thanks nicoddemus!

* Fix for windows users! We were not properly normalizing paths causing source lines not to line up properly. Thanks kingchad1989

2.0.1

* Ensure case is normalized on Windows when comparing paths from XML coverage report Thanks nicoddemus!

2.0.0

* Split Diff-cover and diff-quality's entry point scripts to allow them to be executed using pythons "-m" syntax

Page 8 of 19

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.