search

rsocket / rsocket-cli

Command-line client for ReactiveSocket
Apache License 2.0
71 stars 22 forks source link

Using route with metadata doesn't work #117

Open joshiste opened 3 years ago

joshiste commented 3 years ago

Expected Behavior

send metadata along with the route should work.

Actual Behavior

yields

ApplicationError: JSON decoding error: Unrecognized token 'þԀ琄獥': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false'); nested exception is com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'þԀ琄獥': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
 at [Source: (io.netty.buffer.ByteBufInputStream); line: 1, column: 5]

Steps to Reproduce

$ rsocket-cli -m '{"test" : "value"}' --metadataFormat=application/json --channel --route test -i test --debug wss://localhost:8080/ws

Your Environment

installed via brew: yschimke/tap/rsocket-cli 1.29 on macOS 11.2.1

$ rsocket-cli --version
dev
yschimke commented 3 years ago

Thanks for reporting. I've recently cleaned up the way metadata is sent so it no longer relies on rsocket-java, so hopefully much easier to implement https://github.com/rsocket/rsocket-cli/blob/master/src/main/kotlin/io/rsocket/cli/Main.kt#L237-L250

Is this something you might be tempted to submit a PR for?