Accept query parameters when running locally #197
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
atomaka
force-pushed
the
bugfix/local-querystring
branch
5 times, most recently
from
307b5e5 to
1b6a66c
Compare
atomaka
force-pushed
the
bugfix/local-querystring
branch
from
1b6a66c to
e22b507
Compare
|
Thanks for the pull request. This should be fixed now via (#184). Closing as dupe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #196, I advised that query string parameters do not work when routing locally.
I believe
urlparse.parse_qslemulates the behavior of the AWS API Gateway by only accepting the last query value passed if multiple matching keys exist.