Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path parameter seems to be ignore when Query parameters are added #157

Open
JCorpse96 opened this issue Dec 16, 2022 · 0 comments
Open

Path parameter seems to be ignore when Query parameters are added #157

JCorpse96 opened this issue Dec 16, 2022 · 0 comments

Comments

@JCorpse96
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant