Allow empty sns Subject #240
Merged
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
jakepruitt
suggested changes
Jul 2, 2018
There was a problem hiding this comment.
Nice catch @tcql! Mind adding a quick test to make sure we don't regress this behavior again?
|
hah was already on that @jakepruitt but you reviewed faster than i could write the test! you're fast ⚡️ |
jakepruitt
approved these changes
Jul 2, 2018
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.
Currently, If an SNS message is sent with no Subject parameter, the
$Subjectin the worker script is set to the literal word "undefined". This could be breaking for stacks that respond to multiple Subject values that expect an empty/default subject value to be an unset variable; this was the old behaviourcc @jakepruitt @rclark