refactor(swarm): express dial logic linearly #3253
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Previously, the logic within
Swarm::dialinvolved fairly convolutedmatchexpressions. This patch refactors this function to use new utility functions introduced onDialOptsto handle one concern at a time.This has the advantage that we are covering slightly more cases now. Because we are parsing the
PeerIdonly once at the top, checks like banning will now also act on dials that specify thePeerIdas part of the/p2pprotocol.Notes
I am touching this function as part of #3099 and found it hard to integrate the new callbacks into it.
Links to any relevant issues
Open Questions
Change checklist