8000 fix duplicated response header by nymkappa · Pull Request #5702 · mempool/mempool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix duplicated response header #5702

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

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Conversation

nymkappa
Copy link
Member

Make sure we always return when calling the handleError function

@nymkappa nymkappa requested review from wiz and mononaut December 22, 2024 06:56
@cla-bot cla-bot bot added the cla-signed label Dec 22, 2024
@nymkappa nymkappa requested a review from knorrium December 22, 2024 07:01
Copy link
Collaborator
@mononaut mononaut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested ACK @ [1e3926c]

possibly a little overzealous - only getTransaction, getRawTransaction and getTransactionStatus were missing early returns after handling 404s, but the other handleError usages already return early when necessary.

if we're going to standardize on always explicitly returning handleError, then we should probably extend that convention to the other .routes files too (lightning, mining etc).

@nymkappa
Copy link
Member Author

Tested ACK @ [1e3926c]

possibly a little overzealous - only getTransaction, getRawTransaction and getTransactionStatus were missing early returns after handling 404s, but the other handleError usages already return early when necessary.

if we're going to standardize on always explicitly returning handleError, then we should probably extend that convention to the other .routes files too (lightning, mining etc).

You're right, let me rebase to only fix the actually issue and we can keep a potential refactor for another time

@nymkappa nymkappa force-pushed the nymkappa/fix-response-header branch from 1e3926c to ed28a24 Compare December 22, 2024 14:34
@nymkappa nymkappa merged commit c66f028 into master Dec 23, 2024
13 checks passed
@nymkappa nymkappa deleted the nymkappa/fix-response-header branch December 23, 2024 07:38
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.

2 participants
0