Skip to content
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

Follow up #26

Merged
merged 16 commits into from Nov 9, 2016
Merged

Follow up #26

merged 16 commits into from Nov 9, 2016

Conversation

manthanhd
Copy link
Owner

Allows locking of conversation by a skill for a follow-up.

response.lockConversationForNext();
return next()

Closes #8

Skills can now gain exclusive lock to the conversation for a single followUp. They
should be able to lock again if they need more information from the user.
The lock only lasts for a single next conversation.
Context now is made up of two levels:
Context:
\---lock: 'skill_name'
\---data
       \---...
       \---...

The data part is sent to the skill. Since this is a lower level object, the skill has
no way to access the above layer. This change in structure is useful to store
private metadata that the bot doesn't want the skill to be able to access.
@manthanhd manthanhd self-assigned this Nov 6, 2016
@manthanhd
Copy link
Owner Author

Closed pull on talkify-natural-classifier to fix issue where the built-in classifier would throw exceptions.

This version does not throw synchronous exceptions in the
getClassifications method.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.828% when pulling 72e5272 on followUp into 76791e9 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.828% when pulling b5f44bb on followUp into 76791e9 on master.

… to 2.0.0

This is a breaking change since the final() method now no longer
calls the next() method.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.851% when pulling 7378a23 on followUp into 76791e9 on master.

This is to supress build time errors with various npm modules.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.851% when pulling e40eafa on followUp into 76791e9 on master.

The usage didn't feel very elegant.
Chaining final reads nicer than passing in a random looking
second parameter.
Updated documentation.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.846% when pulling 88e9495 on followUp into 76791e9 on master.

@manthanhd manthanhd merged commit f8cfefa into master Nov 9, 2016
@manthanhd manthanhd deleted the followUp branch November 9, 2016 21:35
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 98.846% when pulling adb5a1d on followUp into 76791e9 on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants