[1.0.0] Consolidate server queue writing to one spot (Part 2)#224
Merged
ChadSikorra merged 2 commits intoJul 18, 2026
Merged
Conversation
…n the handler context to just the interface that exposes no queue writing, only some things that certain operations still need to do.
…e one middleware that handles all server queue writes (aside from auth, which is its own thing)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This makes the middleware carry through a ResponseStream. This lets us use one middleware that handles all server queue writes (aside from auth, which is its own thing). So handers other code now only have to care about producing responses / throwing exceptions and don't need to interact with the queue at all.