Looks cool. I did something similar 2 years ago in a job, and found it super helpful. My favorite feature was that I added an autocompletion/intellisense engine to the editor window in the browser, and then could start creating requests by just ctrl+space-ing. This worked by parsing all input in a failure tolerant fashion, determining at which field the cursor is, and loading possible matches from the interface definition.<p>It's pretty cool to interact with an unknown server API in the same fashion than with an unknown library in an IDE.<p>What I also added was the ability to export requests that one created in the GUI (e.g. as a cURL command including parameters). That made it pretty ease to create requests in the GUI, and then persist and reuse them in other ways.
Hi! Creator of BloomRPC here.
Thanks for the warming welcoming of the client! I’m glad to see lots of positive feedbacks.<p>The client aim to give the best developer experience possible on your day to day usage of GRPC services.<p>We are using it heavily internally and improving it everyday<p>I hope you’ll enjoy working with bloomrpc and that will be soon your GRPC companions
This is really sweet! Definitely fixes one of the missing usability features compared to JSON/REST APIs.<p>Are there any examples of public gRPC APIs that provide their .proto files? I know Google does (<a href="https://github.com/googleapis/googleapis" rel="nofollow">https://github.com/googleapis/googleapis</a>), does anyone else?
looks very similar to a project I worked on last year: <a href="https://github.com/improbable-eng/Dragoman/tree/e8a78c42133569220113d504340cb39445e65fcc" rel="nofollow">https://github.com/improbable-eng/Dragoman/tree/e8a78c421335...</a>
Great job. I ran this on Windows by building from source, it seemed to work for me. I just had to change a couple of things:<p>* Activate Python 2 virtual environment (it didn't work with Python 3!)<p>* Change forward slashes to back slashes in `./node_modules/.bin/electron-rebuild` (I also ran it as a separate command to `yarn install`, not sure whether `&&` would have worked).<p>* Run `npm start hot-server` (rather than `npm start server-hot` in the instructions).<p>* Close the Chrome dev tools, which appeared by default.<p>I must admit I didn't try actually sending a request. Our services are often split into multiple protos with a full relative import (like: import "companyname/project/foo.proto") so you'd need to set the include path for them to work.