Skip to content
This repository has been archived by the owner on Jan 21, 2025. It is now read-only.

Support for replacing a response by a new one #103

Merged
merged 2 commits into from
Sep 13, 2024
Merged

Support for replacing a response by a new one #103

merged 2 commits into from
Sep 13, 2024

Conversation

mathieucarbou
Copy link
Owner

No description provided.

@mathieucarbou mathieucarbou self-assigned this Sep 13, 2024
@mathieucarbou mathieucarbou force-pushed the response branch 2 times, most recently from 8689f21 to 77643fd Compare September 13, 2024 23:02
@mathieucarbou
Copy link
Owner Author

mathieucarbou commented Sep 13, 2024

This really simple PR allows for a very nice feat: ability to override a previously prepared response, in order tp build a new one.

the real sending will happen once the handle exist, not in the send method anymore.

this will allow to have middleware support for response headers too!

@mathieucarbou
Copy link
Owner Author

@DRSDavidSoft: FYI

@mathieucarbou mathieucarbou merged commit ca82a3e into main Sep 13, 2024
46 checks passed
@DRSDavidSoft
Copy link

@mathieucarbou Wow, this is some excellent addition! How does it work internally? Also, what was the previous behavior, for reference?

Thanks for adding this too! 👍🏻

@mathieucarbou
Copy link
Owner Author

@mathieucarbou Wow, this is some excellent addition! How does it work internally? Also, what was the previous behavior, for reference?

Look at the code ;-)

@mathieucarbou mathieucarbou deleted the response branch October 4, 2024 08:16
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.

2 participants