Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: return itself when no change possible in remove_false_nodes #365

Merged
merged 1 commit into from
Jun 26, 2022

Conversation

martinfleis
Copy link
Member

When there is nothing to fix, remove_false_nodes just does nothing but it should rather return the original df.

@martinfleis martinfleis requested a review from jGaboardi June 26, 2022 15:29
@codecov
Copy link

codecov bot commented Jun 26, 2022

Codecov Report

Merging #365 (002af12) into main (319c36a) will increase coverage by 0.0%.
The diff coverage is 100.0%.

Impacted file tree graph

@@          Coverage Diff          @@
##            main    #365   +/-   ##
=====================================
  Coverage   95.9%   95.9%           
=====================================
  Files         13      13           
  Lines       2818    2819    +1     
=====================================
+ Hits        2702    2703    +1     
  Misses       116     116           
Impacted Files Coverage Δ
momepy/preprocessing.py 89.1% <100.0%> (+<0.1%) ⬆️

@jGaboardi jGaboardi merged commit 7697f27 into pysal:main Jun 26, 2022
@martinfleis martinfleis deleted the no_node2 branch June 26, 2022 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants