queryStringParameters set to None when there are no GET parameters

[jops-wtakase]

On Lambda proxy integration enabled environment, if there are no GET parameters in a request path, queryStringParameters should be None instead of {}.

[github-actions]

Welcome to LocalStack! Thanks for raising your first Pull Request and landing in your contributions. Our team will reach out with any reviews or feedbacks that we have shortly. We recommend joining our Slack Community and share your PR on the #community channel to share your contributions with us. Please make sure you are following our contributing guidelines and our Code of Conduct.

[whummer]

LGTM, thanks for this PR @jops-wtakase ! 👍 Also requesting a review from @calvernaz

Looks like the CI builds were not triggered, which can sometimes happen if the CircleCI<>Github connection is broken for your user account. Can you please try this:

1. go to https://circleci.com,
2. sign in with your Github credentials (Single-Sign On)
3. come back here, push an empty commit onto the branch (should hopefully trigger the CI builds..)

Thanks!

[calvernaz]

Hi @jops-wtakase thanks for pushing for this change. I agree None would be a better representation of there are no query parameters, however I think we need to change this change to this code path:

localstack/localstack/services/awslambda/lambda_api.py

Line 575 in 0fb1776

event = construct_invocation_event(

localstack/localstack/services/awslambda/lambda_api.py

Line 608 in 0fb1776

query_string_params = query_string_params or parse_request_data(method, path, "")

parse_qs returns an empty dict if there are no string parameters and that is passed into the Lambda event payload.

[calvernaz]

Thanks for doing this!