We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have a request that looks something like this:
?filter[0][field]=title&filter[0][value]=TestElement&filter[1][field]=category&filter[1][value]=CategoryName
And in the development environment's lambda function the event.queryStringParameters, will be a nested object/array construct like this:
event.queryStringParameters
{ "filter": [ { "field": "title", "value": "TestElement" }, { "field": "category", "value": "CategoryName" } ] }
But in our deployment environment it will be a flat object like this:
{ "filter[0][field]" : "title", "filter[0][value]" : "TestElement", "filter[1][field]" : "category", "filter[1][value]" : "CategoryName" }
It should be the same in both environments.
The text was updated successfully, but these errors were encountered:
🐛 fixed queryStringParameters object implementation netlify/netlify-l…
3bce932
…ambda#54
verified. cc @fool .
Sorry, something went wrong.
fixed querystring parsing netlify#54
4bafb55
Merge pull request #67 from 8eecf0d2/master
ef07a47
fixed querystring parsing #54
does your fix close this issue @sw-yx ? if so I'd close this ;)
fixed querystring parsing netlify/netlify-lambda#54
afe0a62
No branches or pull requests
We have a request that looks something like this:
And in the development environment's lambda function the
event.queryStringParameters
, will be a nested object/array construct like this:But in our deployment environment it will be a flat object like this:
It should be the same in both environments.
The text was updated successfully, but these errors were encountered: