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.
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
Add useJSONContent option for express and sveltekit #41
Add useJSONContent option for express and sveltekit #41
Changes from 1 commit
a945b05
5bd03c3
bd79888
96052d3
81b8290
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 find this very confusing because we cannot assume anyone is familiar with our internal workings, they will not know what
triggerFirstInvocation
is. To me a much more friendly approach would be directly specifying headers that are then forwarded, those can include the content type but are not limitedThere 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.
useJSONContent is not part of the options we allow in
serve
methods for frameworks (see PublicServeOptions). So it won't be visible to users unless they they importserve
from the route likeimport { serve } from "@upstash/workflow"
The reason we need this parameter is because we used to have publishJSON in
client.trigger
. this didn't work because publishJSON addscontent-type: application/json
, which breaks some frameworks. So we usedpublish
. But some frameworks still need the content type to beapplication/json
. sveltekit is one of them.If you have a better alternative to the current implementation we can change it
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.
removed useJSONContent from the public API