Support for running in AWS Lambda with no native extensions #17
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
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.
I removed the dependency on OJ as that makes using this gem in AWS lambda more tricky.
I changed the dependency on rake and bundler to development only as they don't seem to be required for running when you use
bundle install --deploymentas you should when deploying to a serverless platform.I also added support for resolution authorities which allows the Alexa service to try and match synonyms of words provided by the user to an actual slot value.
The only reason I was able to make these changes safely was because of your awesome test coverage! 馃挴 鉂わ笍