-
Notifications
You must be signed in to change notification settings - Fork 7
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
Modify the lambda function to call the split, emotion, sentiment, and question APIs #123
Comments
Time Spent until now: Awaiting update on #119, #120, and #121 to have callable endpoints to continue development of my lambda function. To test, simple pass an empty json, and it shall call the child lambda function. |
Due to a dependency on tasks #119, #120, #121, we have decided to change the scope of this issue. Update:Scope of the infrastructure used to implement this has changed. The latest code I have developed has finished this implementation for #118 as well #120. For the remaining tasks, we have decided to proceed by integrating these features into a single Lambda function, as explained by @shipitsteven in his Pull request to close #162 Work completed:Parent_Lambda_2 currently has integrated the feature to call two of the initially planned issues - #118, as well as #120.
Testing:Parent_Lambda_2 can be tested by giving any sample input as JSON to trigger it. However, I have created a pull request to close this Issue by making some modifications to improve the documentation present. |
The Lambda function needs to call #118 #119 #120 #121 for the feedback, collect all the information for the feedback and reply back using the SWagger specified response.
Update the Swagger to make sure what is returned from the API is also specified in the Swagger.
The text was updated successfully, but these errors were encountered: