Fixed an issue with the None intent when using the parse top_n API #781
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
The `None` intent was ignored when using the `parse` API in conjunction with `intents` and `top_n`
ClemDoum
approved these changes
Apr 5, 2019
Codecov Report
@@ Coverage Diff @@
## develop #781 +/- ##
===========================================
+ Coverage 88.1% 88.19% +0.08%
===========================================
Files 76 76
Lines 4541 4541
Branches 871 871
===========================================
+ Hits 4001 4005 +4
+ Misses 403 401 -2
+ Partials 137 135 -2 |
Merged
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.
Description:
The
Noneintent was ignored when using theparseAPI in conjunction withintentsandtop_nChecklist: