Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add interoperability with JetBrains HTTP Client #4

Open
GauthierPLM opened this issue Mar 15, 2023 · 1 comment
Open

Add interoperability with JetBrains HTTP Client #4

GauthierPLM opened this issue Mar 15, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@GauthierPLM
Copy link

Is your feature request related to a problem?

JetBrains' HTTP Client and JetClient are two HTTP clients residing in the same IDE, meaning they could be used by people concurrently based on their needs / each team member preference.
Currently, one should maintain requests in both format, and JetBrains' HTTP Client being bundled, some may find it cumbersome to switch without an automated way to do so.

Describe the solution you'd like

The plugin would offer to import or export requests from / to the format used by JetBrains' HTTP client. We could even imagine a scenario where requests would be saved in their format instead of JSON, allowing JetClient to become a powerful GUI for JetBrains native format.

Additional context

JetBrains HTTP Client (plugin ID com.jetbrains.restClient) contains a feature to import / export requests to different format (located in com.intellij.httpClient.converters package).
I don't know if their API is stable enough / extendable, but it may be interesting to see if an importer similar to the cURL one could be implemented to easily interact with their requests.

Another solution would be to read their representation of a request, but I have no idea if this is feasible or not.

@GauthierPLM GauthierPLM added the enhancement New feature or request label Mar 15, 2023
@AntonShuvaev
Copy link
Collaborator

Thanks for the feedback, import from .http files definitely makes sense. I'll add it to the roadmap.
Also, I think to add a feature to open request from .http file as a draft request.

Regarding the saving to .http file format instead of JSON, this is not easy to implement, because the .http file format is more restrictive than JetClient JSON format, for example, requests can't inherit auth and headers from folder and also scripts built-in libraries are different.

But I think it could be as an option on collection level, to save requests in JetClient or JetBrains HTTP Client format. And if JetBrains HTTP Client file format is selected, the interface will be limited to the features that are supported by this format. I'll add this to the roadmap too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants