-
Notifications
You must be signed in to change notification settings - Fork 4
refactor: add a hook to SSE client to allow changing the target #526
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
Open
beekld
wants to merge
15
commits into
main
Choose a base branch
from
beeklimt/SDK-2126-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
088418f
refactor: split json parsing/translation for future-proofing client/s…
beekld c990e30
refactor: make the changeset translator a function, not a class
beekld 09b2ef4
refactor: split up a long function into a few smaller ones
beekld 3ba82e1
Merge branch 'main' into beeklimt/SDK-2238
beekld 309eb03
refactor: restore original parameter order
beekld 5b93349
fix: fix the build on linux
beekld dd42ca4
Merge branch 'main' into beeklimt/SDK-2126
beekld ea05ff4
feat(sse): add Builder::on_connect hook for per-connect request mutation
beekld 577746a
fix: make the tests work for both FoxyClient and Curl
beekld 4f540b1
docs: update a comment to be clearer
beekld 653653b
fix: change a shutdown timeout to match the other tests
beekld ab97f30
docs: clarify a comment
beekld 17710f1
fix: handle changing the body in the callback
beekld 4ec32df
fix: override last-event-id in the curl branch
beekld c7d13d8
fix: fix a minor edge case
beekld File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Of course in newer C++ we could make this noexcept without a bunch of hoopla, but not in C++17.
So I am going to suggest we potentially have a try-catch around the connection_hook invocations?
Or we just use strong wording on the signature.
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.
I don't follow. We don't have a try-catch around LogCallback or ErrorCallback. Are you worried about us accidentally throwing from inside the hook?
What would you wanna do if we did? Mark the connection as immediately failed and generate an error?