Insomnia: Multiple proto files

[cristaloleg]

Is your feature request related to a problem? Please describe.
Currently Insomnia doesn't support multiple *.proto files for gRPC. Which breaks our flow 'cause we've multiple files (for services, for events and for models). As you might guess some models(messages in terms of gRPC/protobuf) are not in the same file as services.

Describe the solution you'd like
Having an ability to select few files will resolve our problem. Looks like multiselect during request creation is more than enough (and ability to use gRPC methods from any file of course).

Describe alternatives you've considered
Still using autogenerated clients from terminal or other UI-based alternatives.

Additional context
nothing to add.

[develohpanda]

Hi @cristaloleg! It's interesting that you mention multi-select, we can definitely explore that as an avenue in the future.

We have a task in place for early Jan to work through supporting a root proto pattern for multiple proto files, where the main proto file root.proto imports every other file used by the project. I have a PoC that works in Insomnia, and just need to build some UI on top of it. 🙂

Would this be suitable with your workflow?

[cristaloleg]

Yep, sounds exactly what we would like to see!

Our proto directory looks like this:

❯ exa --tree protos 
protos
├── events.proto
├── model.proto
└── svc.proto

[develohpanda]

Great! Planned for the next release in early 2021 😊

[loganintech]

Just to be 100% clear, does this require a single "root" proto, where all of the rest are in that tree?

We have a use case where we have every proto in a single parent folder, but not all of the protos are necessarily in the same import tree.

[cristaloleg]

Hi @loganintech can you show an example? tree structure or so

[loganintech]

Sure, here's a subset. Basically, the "connection" protos will include models, but aren't related to eachother.

├── atoplevel
│  ├── connection
│  │  ├── service1
│  │  │  └── service1.proto
│  │  └── service2
│  │     └── service2.proto
│  ├── models
│  │  ├── service1
│  │  │  └── service1.proto
│  │  ├── service2
│  │  │  └── service2.proto

[develohpanda]

@loganintech thanks for that, the overall structure is not finalised yet so I'll keep this in mind when we start work on it!