Unescape the path variable

[tobz-nz]

so that characters like { and } are not escaped to html entities.

[tobz-nz]

This allows for variables to be properly defined in the url

[kylef]

@tobz-nz I'm really sorry that we never got back to you on this one. This pull request must've slipped through the cracks.

If you happen to remember any more details, could you share an example Paw request and how its rendered before to help explain the problem that this changeset solves. I think a screenshot would suffice.

[tobz-nz]

hmmm, sorry I don't remembered any details - it was quite a while ago.

My guess would be that if using variables in a url they are getting escaped. something like https://{hostname}/api/users getting output as https://\{hostname\}/api/users or something?

[kylef]

The host component of the URI is stripped out, only the path makes it to the generated API Blueprint example.

I've tested with some characters in the parameters which are reserved and as I would expect, these are percent encoded in the API Blueprint:

[kylef]

If you have { characters in Paw, I don't think it would even be capable of making a request:

[tobz-nz]

🤷‍♂️ Yeah I don't know. It was all too long ago now.
Maybe just close this issue.