We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
getStream requires other or potentially more fields in order to make request to make sense?
https://getstream.io/chat/docs/rest/#product:chat-sendmessagehttps://getstream.io/chat/docs/rest/#product:chat-sendmessage
My assumption is that the above API path is the common usage for getStream.
It requires body property "message" that contains multiple properties. Currently the Novu provider only sends the data "text"
https://github.com/novuhq/novu/blob/next/packages/providers/src/lib/getstream/getstream.provider.ts#L24
N/A
Allow for more or other property fields to be sent to getStream
Novu SaaS
No response
None
The text was updated successfully, but these errors were encountered:
NV-3859 🐛 Bug Report: GetStream missing / or lacks properties in POST requests
Sorry, something went wrong.
No branches or pull requests
📜 Description
getStream requires other or potentially more fields in order to make request to make sense?
https://getstream.io/chat/docs/rest/#product:chat-sendmessagehttps://getstream.io/chat/docs/rest/#product:chat-sendmessage
My assumption is that the above API path is the common usage for getStream.
It requires body property "message" that contains multiple properties.
Currently the Novu provider only sends the data "text"
https://github.com/novuhq/novu/blob/next/packages/providers/src/lib/getstream/getstream.provider.ts#L24
👟 Reproduction steps
N/A
👍 Expected behavior
Allow for more or other property fields to be sent to getStream
👎 Actual Behavior with Screenshots
N/A
Novu version
Novu SaaS
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: