This repository has been archived by the owner on Aug 9, 2023. It is now read-only.
184-Create a subscription adapter for Next.js #203
Conversation
This file contains 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
jadiaheno
changed the title
jadiaheno
force-pushed
the
184-create-a-subscription-adapter-for-nextjs-api
branch
from
47f6dc3
to
8c215d3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is this about
This PR adds a NextJS subscription handler. This handler is in the
subscription-nextjspackage. A nextJs app using this middleware was provided. This handler can also be used with dynamic routes.Issue ticket numbers
How can this be tested?
Run the sample nextJS Api and register a communications. You can also post a communication request.
Known limitations/edge cases
NA