bugfix(microservices): let use unicode characters in TCP Microservice… #1795
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.
… messages
add own json-socket implementation
#1734
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #1734
What is the new behavior?
Unicode characters in TCP Microservice messages don't cause errors
Does this PR introduce a breaking change?
Other information
The core algorithm was borrowed from original json-socket package (https://github.com/sebastianseilund/node-json-socket). Basically all unnecessary code was removed, only the core functionality was kept.