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

bitswap/network: split Routing in two in interface #580

Closed

Conversation

Jorropo
Copy link
Contributor

@Jorropo Jorropo commented Feb 16, 2024

This change does nothing, the reason it exists is because two different branches want to independently remove methods from this interface, this decouple the two methods allowing to do so without git conflicts.

This change does nothing, the reason it exists is because two different branches want to independently remove methods from this interface, this decouple the two methods allowing to do so without git conflicts.
Copy link
Contributor Author

Jorropo commented Feb 16, 2024

Copy link

codecov bot commented Feb 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (79cb4e2) 65.56% compared to head (911f4e9) 65.34%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #580      +/-   ##
==========================================
- Coverage   65.56%   65.34%   -0.22%     
==========================================
  Files         207      204       -3     
  Lines       25597    25526      -71     
==========================================
- Hits        16782    16680     -102     
- Misses       7336     7362      +26     
- Partials     1479     1484       +5     

see 16 files with indirect coverage changes

@Jorropo
Copy link
Contributor Author

Jorropo commented Feb 16, 2024

Forget this, that doesn't help since then it has conflicts on the ipfs_impl.go implementation and theses can't be solved without a dependence (as there is a single argument for both codepaths).

@Jorropo Jorropo closed this Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant