URL path variables are not replaced if followed by a dot

[fireattack]

Describe the bug

When path parameter is immediately followed by a dot, the character afterwords are considered as part of the path parameter. And there is no way to split the two.

Example: https://example.com/api/:id.json

To Reproduce
Steps to reproduce the behavior:

1. Create a new request tab.
2. Paste in the above link
3. Check path parameter part.

Expected behavior
The key should "id", not "id.json".

Screenshots

App information (please complete the following information):

• App Type Native App
• Postman Version 7.22.1
• OS: Win7x64

Additional context
The bug was firstly reported at #4423 and later redirected to #2427. Both of these two issues are closed despite the bug is still present in newest version. I think relying on closed issue(s) for discussion of an existing bug not the right way to do it, so I open this new ticket to reflect the fact that the bug still exists.

[whyvez]

It would be nice to be able to do something like: https://example.com/api/:id.:format which would map to two path params of id and format.

[jayarjo]

How many times this bug has to be reopened?

[dzmitry-kankalovich]

I just really wish someone at Postman would spend some time on, you know, covering their fix with unit tests. Because it's broken again.

[fireattack]

It indeed is weird this hasn't be fixed. I encounter this issue semi-frequently when using Postman. I'd guess others would find so too.

[coditva]

Hey everyone, this issue has been fixed and is now available in v9.23 onwards. 🎉
Please update the app and let us know how it goes. 🙂

[shubhbhargav]

Re-opening the issue due to a bug where the variable is not getting resolved when the request is sent: #2805 (comment)

[coditva]

Update: The bug has been identified. The issue is fixed and will be rolled out with v9.25 release in the next few days.

[coditva]

Update: The fix is now available in v9.25.x onwards. Closing the ticket; please re-open if facing any issues. 🙂