Support for path parameters

[vboctor]

Postman supports ":param" in path as a first-class concept which is convenient compared to having to use pre-request variables. It is also useful when importing a Postman collection into Bruno to have support for such case.

If for some reason it is not desired to add such support, then during importing Postman collection convert ":param" to "{{param}}" and add it to the pre-request variables. Though it will be much better to support path parameters.

[Kenneth-Macharia]

Adding just this one thing, say in your next release, will make me shfit from Postman immediately

[DrGrognon]

+1
This is a must for postman compatibility.
Furthermore, i serve an important self-documentation purpose as it make explicit "this is a query param" when usual variable can be env/api version/whatever

[1Mark]

+1

[mikekosulin]

Any updates?
It’s terrible to use API tool w/o path variables.

[RemekGdansk]

Looks like there is a PR for it: #484

[theMK2k]

+1 Insomnia does, too

[casperghst42]

This is right now the only thing which keeps me from switching from Postman.

[TheRealBenForce]

This is right now the only thing which keeps me from switching from Postman.

same

[mikekosulin]

This is right now the only thing which keeps me from switching from Postman.

same

Soon:
#484 (comment)

[pasalino]

same, is very useful to switch from Postman

[mikekosulin]

#484 has been merged!

Thanks, @game5413

[magnetik]

What a great news ! This was the main blocker for us to migrate to bruno.

Looking forward for a release including this.

Good job to everyone involved! ❤️

[Kenneth-Macharia]

Can’t wait, either, super excited!On 23 May 2024, at 11:43, Baptiste Lafontaine ***@***.***> wrote: What a great news ! This was the main blocker for us to migrate to bruno. Looking forward for a release including this. Good job to everyone involved! ❤️ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[yulin-dong]

Which release has included #484? I don't see it in any release note.

[Its-treason]

Which release has included #484? I don't see it in any release note.

It is not merged on master, there is another open PR with the feature: #2357

[helloanoop]

We merged #2357 to main today.
The main build will go out on Tuesday June 4th 2024.

Meanwhile we will also share a dedicated build later today so that community can test this and report any issues.

Thank you so much @game5413 for working on this.
Thanks @edbrannin @bsleczko @Its-treason for the reviews.
Thanks @sanjai0py @lohxt1 for getting this polished and merged.

[helloanoop]

Please test this build out and report issues if you find them: https://github.com/usebruno/bruno-nightly-builds/releases/tag/v1.19.0-31may2024

[magnetik]

I've tested it. When loading a request that have a :param in the URL created in the 1.18 version, the box that allows param to be configured is now shown.
Working fine when editing it afterwards.

[noavarice]

Will it be possible to escape colon? You can't use colons in URLs in Postman adequately bc of path parameter support. Colon is reserved symbol in URLs, so it's kind of strange to use such symbol for embedding stuff at the syntax level (at least without escaping)

[Ukrainis]

Hello to all.
Having an issue with pathParams, created a bug: #2439 .