Not able to input streaming messages in cli mode

[frxstrem]

I'm trying to send a stream of messages in cli mode, but I can't find any information about how this is done. I tried the two most obvious ways (in my mind at least):

• Sending objects as an array [{}], but evans complain about an unexpected character [. (failed to read input from JSON: Bad input. Expecting start of JSON object: '{'. Instead got: [.)
• Sending objects as a JSON stream (one JSON object per line), e.g. the regular output from jq, but evans complains about unexpected EOF. (failed to read input from JSON: EOF)

Is this even possible, and if it is, could you point me in the right direction to get this to work? And possibly add some documentation somewhere about it?

[ktr0731]

Thanks for pointing to a problem related to streaming in CLI mode!

Right ways to send requests to streaming APIs are (JSON inputs, packages, services are pseudo):

1. server-side streaming

$ echo '{ "name": "a request" }' | evans --package api --service ServerStreamingAPI

2. client-side streaming (send two requests)

$ echo '{ "name": "request1" } { "name": "request2" }' | evans --package api --service ClientStreamingAPI

3. bidi sreaming

$ echo '{ "name": "request1" } { "name": "request2" }' | evans --package api --service BidiStreamingAPI

You might think that inputs which are sent as client-side/bidi streaming API requests look strange.
In the implementation, Evans decodes input JSON text as a proto.Message sequentially. So users have to send JSON with the above format.

I'm planning to add more documentation to Evans repository. (#57)
But, I think it takes a little until I begin.

[frxstrem]

@ktr0731 Would it be possible to also support newline as an object delimiter? That way evans would work nicely with tools such as jq.

[ktr0731]

Could you show me an example input?

[frxstrem]

Oh nevermind it already seems to work after all, I must have done something wrong when I tried previously...