BUG FIX: fixed the get_named_parameter function to properly handle th… #375
Conversation
This file contains hidden or 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
…e case where the parameter is not found in the event object.
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…e case where the parameter is not found in the event object.
Issue #, if available:
Description of changes:
In
lambda_handler()when callingget_named_parameter()its considered as best case that "booking_id" will exists. If it does notnext()will raisestopIterationexception leading further failure. Changes made to avoid stopIteration exception and provideNONEwhen correct key does not exists.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.