API provider ignoring query parameters
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
Description
Query parameters on API provider operations are always null
. The query parameter is passed to the unified data shape but the value is not set correctly at runtime. Instead the parameter value is always null
.
You can reproduce this with a simple GET operation that uses a query parameter and log the body right after entering the operation flow.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Should a server ignore unrecognized query parameters OR ...
Should a server ignore unrecognized query parameters (i.e. not defined in the OpenAPI document) or should it throw a 400 exception?
Read more >Solved: Query params are ignored - The Meraki Community
i've tried adding different keys and values under 'Query Params' to filter the results. These keys and params seem to be ignored however....
Read more >Extra Query parameters in the REST API Url - Stack Overflow
Option 1 : Ignore the extra invalid queryparam and serve the request. Option 2 : Throws bad request message to the client. Thanks...
Read more >Ignoring Query String Parameters - SmartBear Support
To do this, enable the Ignore dynamic URL parameters property of your project and specify the list of parameters to ignore.
Read more >Crawler: IgnoreQueryParams - Algolia
Filters out specified query parameters from crawled URLs. This can help you avoid indexing duplicate URLs. You can use wildcards to pattern ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
api-provider-test-export.zip
This should crash right after the application gets started
The crashing is no longer a problem for me. The API Provider doesn’t ignore query parameters anymore, not required parameters can be addressed with Conditional flows. Verified by QE.