-
Notifications
You must be signed in to change notification settings - Fork 42
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
refactor: error message for missing token and cleanups #168
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey
This approach was functional but not optimal in terms of clarity and efficiency.
The efficiency here is equal, as the changes are noop. In terms of clarity tho, we rather prefer what we had in places I mentioned.
We're happy to merge the rest of changes tho if you'd like to remove those two
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks 👍 the CI issue is likely a new clippy finding that came with new toolchain
It looks like there is another issue, we have a requirement for commits to be signed. Would you mind signing the commits you made? |
Head branch was pushed to by a user without write access
Signed the commits and updated. Please check. Thank you. |
looking good, thanks @codeesura |
Summary
This pull request introduces a refactoring to the
fetch_bridge_multiaddrs
function in codebase, specifically targeting the way TCP protocol filtering is handled.Changes
Previously, the function utilized a
.filter()
and.map()
combination to process Multiaddr elements, which could include TCP protocols. This approach was functional but not optimal in terms of clarity and efficiency. To enhance the code quality, I've refactored this segment using.filter_map()
, which combines filtering and mapping in a more concise manner.