-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Payload must (?) be valid JSON #18
Comments
I have a legacy application where I cannot change the payload format, so I think that makes already two valid use cases for non-JSON payloads. As a workaround I implemented an option to use "raw" payloads some time ago, but I am unsure if it is implemented up to standards of the author: master...Ingramz:master |
Hey guys! How about a |
Check out #21. What do you think? |
Hi Andy. Thanks for responding so quickly. I think that sounds like an awesome idea. |
Yeah, looks good to me. The idea of serializer/deserializer suits well the packeted nature of the communication, allowing to return more complex objects as well. |
Published as |
Hi Andy,
Thanks a lot for your module and the work you've invested in it.
Are there any plans to support notification payloads that are not valid JSON? I was hoping to use it for passing an ID (UUID), but it barfs with:
I can possibly modify the notifying code to create a JSON payload, but it seems like an 'unnecessary' overhead, and it should be up to the consumer to decide what to do with the payload.
Cheers,
Steve
The text was updated successfully, but these errors were encountered: