-
Notifications
You must be signed in to change notification settings - Fork 22
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
Allow to send raw jtoken/jobject instead object #321
Comments
Hi @mcdis. Can you elaborate on your use case please? |
Hi @mattheworiordan! |
Thanks for the response, will get @withakay to look at soon. |
Hi @mcdis. There might be a small issue depending on which version of the library you are using. We currently bundle json.net with the ably binary in .net and xamarin to stop people having issues if they are using older version of the json.net. I don't know if exposing a jtoken class will be the same as you are using. Currently there is a way to pass json directly. You can package it an encoded Message object as described in this ticket: #92 (comment) You can pass a json object to ably at the moment and you will get a JObject back on the other side. I'm sure this will work fine if the services are .net core but need to test it in .Net Framework. If you want to send a json string and you don't want ably to try and decode it on the way back then you can create a message with a custom encoding and the library won't touch the json string so you can choose whether to parse it or not. Here is a test showing how that works:
|
Allow to send raw jtoken/jobject instead object in IRestChannel.PublishAsync
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: