Show HN: Ezy – open-source gRPC client, alternative to Postman and Insomnia
Looks promising. I have to say this is still really rough, though.<p>Some feedback after 5 minutes of testing:<p>* It doesn&#x27;t remember your &quot;environment&quot;. So if I call endpoint A and then click on endpoint B to try that, it forgets which environment is being targeted.<p>* Similarly, metadata is also specific to the request. If you use metadata for providing authorization headers, that means you have to enter the metadata separately every time you make a different request; there&#x27;s no way to share metadata as an &quot;environment&quot;.<p>* If you create a collection and click &quot;Create&quot;, and it errors saying an imported proto resource wasn&#x27;t found, the entire collection disappears.<p>* The app uses the proto schema to show a list of endpoints, but it doesn&#x27;t know anything about the message and response schemas, and you can&#x27;t browse the types? It seems tedious to have to manually enter the request as a JSON payload.<p>* Similarly, response is shown in JSON, rather than Proto data. So I can&#x27;t see what the returned types actually are.<p>* The &quot;Request&quot; and &quot;Metadata&quot; editors are super laggy to the point of being unusable. It takes several seconds for what I type to appear in the editor, and my computer&#x27;s CPU usage goes to 150% while it&#x27;s sitting there doing nothing. Is there some kind of autocompletion that&#x27;s supposed to kick in that&#x27;s going into overdrive?<p>* Clicking on an endpoint adds another tab. Click around and you end up with dozens of tabs. Seems a bit pointless.<p>* No support for setting HTTP headers or seeing the returned headers.