Iteration Plan for Insomnia Core

[nijikokun]

This plan captures items we are focusing on in the core at a higher level. We will ship features as they are ready to be released. This list / post may change from time to time.

Plan Items

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team

General

• Update electron [Build] Update Electron #1847 @gschier
• Change duplicate request mapping so it doesn't conflict with multi-select [Bug] Ctrl-D with Sublime key map #685

Environments

• Scope responses to active environment [Feature Request] Option to scope Request Chaining per Environment #1895
• Grouping responses and tokens under environments [Usability] Stale OAuth access token used after switching environments #260 [Bug] Switching environments will re-use a stale chained request value #669
• Filters cannot operate on values rendered from Template Tags [Bug] Extracting substring to token value doesn't reference tag properly #1809

Import / Export

• Support importing all Postman export types Import bulk of postman collections #691
• Export as OpenAPI v3 [Feature Request] Export as OpenAPI #1778
• Improve performance when importing large specs Response preview: right-click a value to create/save a variable #1834
• Honor default variables when importing OpenAPI [Bug] OpenAPI import does not seem to honor default variables in servers declaration #1640

Networking

• ⚫️ GRPC / Protobuf support
• Update node libcurl & support for HTTP/2 [Feature Request] Support HTTP/2 requests #997
• Add ability to configure/disable automatic URL encoding [Feature] Configurable URL Encoding  #605 [Feature Request] Automatic encoding of $ breaks OData APIs #592 [Bug] Do not encode sub-delim characters in query part of URL #604
• Friendlier JSON viewer in Preview mode [Feature Request] Allow a way to show all the accepted options for a query parameter #1802 (maybe with Create Friendly JSON Viewer #494?)

Plugin System

• Add support for enabling / disabling plugins [Feature Request] Enable / Disable Plugins #1610 @develohpanda
• Add support for accessing non-text based content from plugin context [Feature Request] Ability to access non-text body content from plugin context #1788
• Add support for cancel hooks [Feature Request] cancelHook #1608
• Ability to define action buttons on template tags [Feature Request] Allow prompt values to be cleared #1456

---

Deferred Items

• Add support for WebSockets [Question] Websocket Support? #528 [Feature Request] SSE/EventStream debuging #1345 [Feature Request] Support Keep-Alive Connections #1842
• 💪 Add preflight / cors check during requests [Feature Request] CORS and preflight requests #687
• 💪 Add enum support [Feature Request] Import Enumerations from Swagger file #1806 [Feature Request] Allow a way to show all the accepted options for a query parameter #1802
• 💪 Add ability to define UI plugins [Feature Request] API for UI plugins #1383
• 🔵 Multi-window support [Feature] Multi-Window Support #667

[jeffdoolittle]

GRPC / Protobuf Support happening in the near future would be awesome

[dingyaguang117]

Really need OpenAPI 3 exporter!

[mtsmachado8]

Really need OpenAPI 3 exporter too! thanks for considering it...

[edbrannin]

🔵 Multi-window support #283

I don't think that's the issue number you're looking for.

[gschier]

@edbrannin thanks for pointing that out. Just updated the issue number to the correct one (#667)

[m-v-k]

Really Really need Team Collaboration (the $8,- one) support for Single Sign On (we use AzureAD but any openid-connect provider should be possible).
i cannot manage 80+ developer accounts in all tooling that my company uses :(
i want to move to insomnia for all our devs, but we really need this.

[gschier]

We hear you @m-v-k! 😄

We're aware of the issues larger orgs face by not supporting SSO and it's something we'll be working towards going forward.

[nijikokun]

We were definitely overly-ambitious when we made this post originally. Updated accordingly, and it may get updated again with a proper timeline.

[mpern]

Any chance that #203 gets added to this roadmap?

It has a lot of upvotes and is a glaringly missing feature of Insomnia.

[nijikokun]

Any chance that #203 gets added to this roadmap?

Looking into it to see if we can scope something out for the application.

For now, I'm wondering if this plugin would help?

[crash7]

Any chances that you port the git sync from the designer back to insomnia core? the designer in debug mode is basically insomnia core 😕

[nijikokun]

Any chances that you port the git sync from the designer back to insomnia core? the designer in debug mode is basically insomnia core 😕

We have plans for this but it will be later in the year

[Nisgrak]

I think #1778 should be a priority, with that you improve the interoperability with Postman. We would import Insomnia collections in Postman.

[softmarshmallow]

+1 for gRPC, no other client supports gRPC yet (such postman, postwoman), this will bring insomnia to the next level.
(yet postwoman already supports websocket, mqtt, ..)

[joshpaulchan]

Apologies if this is the wrong place to raise this, but I'd like to work on:

Add support for WebSockets #528 #1345 #1842

I'm not actually sure if someone's currently working on it. I've read the contributing guide and through the relevant issues; is there an existing project or ticket to track the work + implementation plan?

[nijikokun]

I'm not actually sure if someone's currently working on it. I've read the contributing guide and through the relevant issues; is there an existing project or ticket to track the work + implementation plan?

Hi @joshpaulchan,

We haven't started one for Websockets just yet. The team and myself included have been working through GRPC, which has some similarities in the way responses should be handled (streaming). Our thought process is once we have finalized our plans for the GRPC feature-set, we can use these assets and documents to begin framing how we want to approach Websockets.

That said, we are definitely open to proposals / RFCs for this featureset with wireframes / mocks.

Feel free to ping me (Niji) on the Insomnia slack where I can share some existing wireframes for GRPC if you are interested.

Also, apologies for the delayed response. Past two weeks have been quite heavily packed!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[filfreire]

@wdawson I'm going to close this one as I think it's since no longer applicable or displaying our current plans.

We can probably try some sort of alternative for this, either creating something like a public GitHub Project, or creating some sort of public view of linear where we can show folks which major chunks of work we are doing or a public facing roadmap.

Some examples we could use for guidance:

• VSCode
• GitHub