torressa / cspy

A collection of algorithms for the (Resource) Constrained Shortest Path problem in Python / C++ / C#
https://torressa.github.io/cspy/
MIT License
77 stars 24 forks source link

Faster and uglier implementation of the bidirectional algorithm for v1.0 (Sourcery refactored) #71

Closed sourcery-ai[bot] closed 3 years ago

sourcery-ai[bot] commented 3 years ago

Pull Request #70 refactored by Sourcery.

If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

Run Sourcery locally

Reduce the feedback loop during development by using the Sourcery editor plugin:

Review changes via command line

To manually merge these changes, make sure you're on the patch66 branch, then run:

git fetch origin sourcery/patch66
git merge --ff-only FETCH_HEAD
git reset HEAD^
sourcery-ai[bot] commented 3 years ago

Sourcery Code Quality Report

✅  Merging this PR will increase code quality in the affected files by 0.25%.

Quality metrics Before After Change
Complexity 0.47 ⭐ 0.21 ⭐ -0.26 👍
Method Length 57.40 ⭐ 57.20 ⭐ -0.20 👍
Working memory 7.88 🙂 7.85 🙂 -0.03 👍
Quality 76.59% 76.84% 0.25% 👍
Other metrics Before After Change
Lines 111 107 -4
Changed files Quality Before Quality After Quality Change
test/python/tests_issue32.py 76.59% ⭐ 76.84% ⭐ 0.25% 👍

Here are some functions in these files that still need a tune-up:

File Function Complexity Length Working Memory Quality Recommendation
test/python/tests_issue32.py TestsIssue32.setUp 0 ⭐ 172 😞 8 🙂 65.02% 🙂 Try splitting into smaller methods

Legend and Explanation

The emojis denote the absolute quality of the code:

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.


Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Let us know what you think of it by mentioning @sourcery-ai in a comment.