Does not support array query string parameters
See original GitHub issueaws-serverless-express cannot parse array query string parameters
For example ?a=1&a=2
exposes only {a: 1}
to express. Normally this would result in {a: [1, 2]}
API Gateway supports array query string parameters using multiValueQueryStringParameters
instead of queryStringParameters
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:13
- Comments:12 (1 by maintainers)
Top Results From Across the Web
How to pass an array within a query string? - Stack Overflow
I want that query string value to be treated as an array- I don't want the array to be exploded so that it...
Read more >Arrays in query params - Medium
Arrays in query params. The same way there is no concensus over how objects should be represented in query parameters, there is no...
Read more >Does not support array query string parameters #214 - GitHub
After searching around the code a little, I came up with a temporary hack in my code that overrides the queryStringParameters field in...
Read more >Python: Why you can't use Arrays in Query Strings with ...
I found that Requests uses urllib 's urlencode function to encode query parameters here and here. The culprit was urlencode ! urlencode stuffs...
Read more >Fun stuff: representing arrays and objects in query strings
Decoding a query string into an array is done with parse_str. It supports the ... Yep, URLSearchParams does not support objects as values....
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
Wow would be really nice to get this merged in!
Hi @pejulian,
For my project what I ended up doing is patching the library manually inside the node_modules dir, and converting that into a patch by using patch-package.
What patch-package does is, it creates a patch that gets applied after yarn install.
I know this is not an ideal solution, but this bug was wasting too much of my time on workarounds…