-
Notifications
You must be signed in to change notification settings - Fork 361
impl http multi value query str parameters #59
New issue
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
impl http multi value query str parameters #59
Conversation
// multi valued query string parameters are always a super | ||
// set of singly valued query string parameters, | ||
// when present, multi-valued query string parameters are preferred | ||
builder.extension(QueryStringParameters( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
abstracting over both cases was a conscious decision. I've found multi valued query string parameter cases awkward to work as two separate collections. the thought process behind making StrMap
represent both cases was inspired by HeaderMap
which abstracts over single and multi valued headers. The semantics here are documented in the public api for users
…alue-query-str-parameters
Thanks! Looks solid to me. |
(There are merge conflicts. I think I merged out of order. I can fix them tomorrow, or you can. Up to you.) |
…nto lambda-http-multivalue-query-str-parameters
pushed conflict resolution commit |
Issue #, if available:
Description of changes:
this is a follow on to #58 ( which adds support for (de)serializing multi valued headers. since this is a pull against master it will also contain those changes since this was branched from. That pull should be reviewed first and this second.
There will be one final pull to tie the bow and make the lambda-http crate transparently handle both api gateway and alb events.
By submitting this pull request