Url segment params

[adomurad]

Hi,

First of all: I love this fork and the ideas behind it <3

Working with insomnia I have always missed one feature - url params.
Something exactly like the query params from insomnia, but for the url path segments:

[andrej-urvantsev]

I created a duplicate of this request(and closed) #16

My suggestion is to just follow current design: create a new tab "Path var" or alike and copy-paste "Query" tab and make it work. And leave redesign discussions for a later stage.

[archywillhe]

good idea; I will sort this out for v0.2.0

[yjlcoder]

I think tab "Query" is for query parameter, and this :userId is a path parameter.

Normally I use an environmental variable to do this:

[adomurad]

I'm not saying to delete the "Query" tab!
This is just my low-quality mockup 😄

I'm just proposing to add a new tab that looks exactly like the "query" tab, that will allow me to parametrise my path segments.

I have a lot of requests like:
https://my-domain.com/company/COMPANY_ID/contract
Where I need to do a couple of request with different COMPANY_ID to test stuff and check responses to solve some problems...
And going into environment variables every couple of seconds to change the var is too slow for me - right now I'm just changing the url...
And I have ~30 of those requests - so I would have to have ~30 different variables - and it would be hard to find the specific var for specific request.

[yjlcoder]

Thanks for the explanation. Yep it's my fault I misread the description. I incorrectly thought we were gonna reuse "Query" tab for path parameters. I agree it's better to have a separate tab for path params.

[TCB13]

I still don't get it. The current environment variables do what you want...

[andrej-urvantsev]

That's what I meant - we already have Query and Headers tabs. So, following de facto convention, lets add a new tab "Path var". It's not perfect, since I, as a user will have to go through the tabs to change request parameters, which lacks visibility. But at least it will be consistent with current design.

[archywillhe]

I've added a Segment Params View under the Query tab for now (It will only show up if it detects :{something} in the URL). Since that's where the URL Preview is, I think it's natural for Segment Params to be located underneath.

I will implement a new Variable tab in the next update - for Variables I really want them to be able to used across all fields - so after that, we can directly export an Insomnium Request as an async function into Typescript, Python, etc and be used in an existing codebase

[archywillhe]

just added first class support for segment params - 4aa7e50

v0.2.0 is out now. (homebrew & flathub releases coming soon (+ macOS notarization & Windows signing))

Let me know what you guys think (or if you guys ran into anything weird)

url-segment-.mov

[CodingMomentum]

Thanks for this! I've just come over from insomnia (see #92), and had been utilizing the insomnia-plugin-path-parameters plugin, but this is a great implementation of this, as the plugin never rendered the url correctly, despite sending the correct thing.

That'll save me a plugin. 👍

[bigben-fr]

Hello,

When I generate cURL code with segment parameter in URL, it keeps the variable instead of the value, example :

https://localhost:443/api/v1/books/:isbn
instead of
https://localhost:443/api/v1/books/9782840910121

Is this possible to replace the path param segment by its value ?
When I clic on </> Generate code from the drop-down menu close to the request or from
</> Show CURL code, etc from the drop down menu close to the Send button ?

My configuration :
Version: Insomnium 0.2.3-a
Build date: 29/10/2023
OS: Windows_NT x64 10.0.19045
Electron: 25.8.1
Node: 18.15.0
Node ABI: 116
V8: 11.4.183.29-electron.0
Architecture: x64