-
Notifications
You must be signed in to change notification settings - Fork 71
Ensure that the initial request.signal is passed to the wrapper #848
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
Conversation
🦋 Changeset detectedLatest commit: 20730c3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Thanks for the review James! |
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.
LGTM, but it will need to wait for the next version of aws to be released.
I'll do one release later today
Hey, I'm back from vacation! Thanks @sommeeeer for working on this, I'll update aws soon. Can #847 be closed and this one used instead? |
Welcome back @vicb ! Yeah, I'll close that one right now. |
Changes LGTM but we need to bump aws before merging this I think? |
Thanks for the review Victor. Yeah, it needs latest AWS |
618a3e7
to
98e6d7d
Compare
rebased on HEAD (aws 3.7.6) |
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.
Thanks for the update @sommeeeer, let's merge as CI gets green!
For opennextjs/opennextjs-aws#952
Pass along the original
AbortSignal
to the wrapper.Will make
request.signal.onabort
work in route handlers.Should also close #691