Path parameter seems to be ignore when Query parameters are added
JCorpse96 opened this issue · 0 comments
I am new to flogo and I started to use it with the Flogo Web UI.
I tried creating an application with a Receive HTTP Message Trigger and in the path definition I wrote the following:
/flightbooking/:class?firstName=first&lastName=last
When I test it through the browser, it seems like the path parameter is ignored and only the query parameters are considered.
The response I receive is the following:
{"Class":"","Cost":468,"DepartureDate":"02/03/2023","DeparturePoint":"PAR","Destination":"SFO","FirstName":"first","Id":533,"LastName":"last"}
But then I tried creating another Flow action in the same App, also with a Receive HTTP Message Trigger, but this time with the following path:
/hello/:name
And then the path parameter is not ignored, because I receive it in the response:
{"Hello":"Test"}
In both cases I am mapping the Trigger Output to the Flow input in the same way:
$.pathParams.class
$.pathParams.name
Can you help with this issue? Is there something that I need to be doing differently?
If you need more info on other parts of the flow, just let me know!