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

Adjust existing PRs for the new reply.sent handing #3444

Conversation

sergejostir
Copy link
Contributor

@sergejostir sergejostir commented Nov 14, 2021

Checklist

This PR adjusts some of the already merged PRs, so they are in line with the new way that reply.sent is handled (introduced in #3072).

#3261 & #3285: kReplySent does not exist anymore. We can simply delete those lines since they don't have any effect.

#3318: With the new way that the reply is handled, we do not have to do anything manually any more. Only the test had to be adjusted because of the reasoning explained in #3132.

@sergejostir sergejostir force-pushed the pr/adjust-existing-prs-for-the-new-reply.sent-handing branch from 1dc6d13 to 21f7050 Compare November 14, 2021 17:58
@mcollina
Copy link
Member

Why a separate PR? Couldn't we just cherry-pick the commit?

@sergejostir
Copy link
Contributor Author

sergejostir commented Nov 14, 2021

Probably, but how can I propose that? And how would that be better than a PR?

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@mcollina
Copy link
Member

I have updated the next branch and now I understand what you mean. This can land.

@mcollina mcollina merged commit fd8503a into fastify:next Nov 23, 2021
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants