-
Notifications
You must be signed in to change notification settings - Fork 18
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
Receive function of consumer is removing blank spaces at the end of message #45
Comments
Hi @thejams - I'll take a look at this over the next week too to see if I can resolve the current behaviour. In the mean time as a (somewhat hacky I admit!) workaround do you have the option to add a non-blank character to the end of the messages when they are sent, and trim that character off when you receive them in your application code - as that approach should honour the blank spaces that exist at the end of the current message text. |
hi @matrober-uk thank you very much for the reply, i did a workaround similar to what you mentioned and it works for now, thanks again for the reply dude |
Prevent trimming of whitespace on receive - #45
Fix merged to main under #48 Fix included in new tag v1.6.0; |
Hello, im currently making a produce / consumer application, and everything works fine except that when the consumer receives the message somehow i don't know why the blank spaces at the end of the message send by the producer are gone, somehow the consumer is making some kind of a trim to the message, it is possible for this not to happen ? because i need those blank strings at the end of the message, those belong to the original message and i need them
The text was updated successfully, but these errors were encountered: