Closed iancullinane closed 5 months ago
The way this is expected to work is to configure the path as /v1/endpoint/{UserId}
. This should make a "UserId" entry appear in the "Path params", whose value you can set to {{ vars.uuid }}
.
A similar configuration from the example project:
I understand that this behaviour is confusing and we'll discuss if we can do anything to improve this.
A fix for this has been implemented and was released with the newest beta release. It will be included in the next stable version.
Kreya 1.14 has been released
Describe the bug When trying to use a REST slug with a variable, there seems to be some unexpected behavior. I have a slug that takes a
uuid
, not a query param. I assumed I could use a variable for this but it appears to be failing, those failures also appear to inject strings that no longer exist.To Reproduce Steps to reproduce the behavior:
/v1/endpoint/{{ vars.uuid }}
.{ vars.uuid
as the "Key" and nothing for the value.uuid
in the expected position.Addtionally, and I can't get the kreya environment to stop this behavior now that it has happened.
{{ vars.uuid }}
still have the query param (egv1/user/%7D?%3AownerID=%7D
Expected behavior Using a variable in the slug injects it appropriately.
Screenshots If applicable, add screenshots to help explain your problem.
Environment (if possible, copy the information from the error dialog or the About menu):
Context
When adding a variable at the end of the slug the following appears in Path Params, not sure if this is expected: