Forum Discussion

Guru2's avatar
Guru2
Occasional Contributor
3 years ago

How encoding/Decoding of Grpc proto parameters processed in ReadAPI during .proto file import

In our project we have requirement to test the grpc protocol using unary operation. Able to import .proto file successfully in readyapi, but when created the test case using the imported file, the or...
Configuration
Function Tests
REST
Test Results
richie's avatar
richie
Community Hero
Hey TNeuschwanger,

Just a follow up FYI for you regarding the json order/unorder (unorder....ia that even a word? Never mind...rhetorical!)

The definition of a json object is an "unordered list of name/value pairs".
If you want the contents of an object in a particular sequence, you have to do things like embed it in an array, etc.

Cheers

Rich
sonya_m's avatar
sonya_m
SmartBear Alumni (Retired)
3 years ago

Thanks, Community!

Guru2 please let us know if the advice helps!

  • Guru2's avatar
    Guru2
    Occasional Contributor
    3 years ago

    Hi Sonya,

     

    Thanks for asking. My query was not solved because this is not a json request/response. Still could not understand how readyapi encodes the request data to server when the grpc request created using the unary call imported from .proto file.  So tried modifying the default request data in the grpc unary call based on how we implemented in our code. That modification did not helped, it throws "invalid input length" error after modifying. Any suggestions how to proceed further? How this request data is being set when creating grpc request using the imported API definition? Kindly let me know. 

     

     

    Thanks,

    Guru 

  • Guru2's avatar
    Guru2
    Occasional Contributor
    3 years ago

    When sending request from readyapi to some server using grpc. Are some bytes getting padded in the json request or its re-ordered? How this encoding is happening in readyapi while sending request? Kindly let me know your thoughts on this.

     

     

    Thanks,

    Guru