You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Amazon Lex V2, Alexa and potentially some other NLU systems support multi-valued slots, which are - as the name suggests - slots that can have a list of values.
Instead of having to go into the native interpretation, it should be possible to access lists of entities directly.
Example:
Given the phrase "Turn on {Lights}" with the slot Lights being multi valued, the utterance "Turn on the Desk Lamp, the Ceiling Lights and the Outdoor Lights" would match Lights as being ["Desk Lamp", "Ceiling Lights", "Outdoor Lights"]
Current Behavior
The only way to get the list of matched entities is to use jovo.$entities[entityName].native.
When multiple values are matched through Lex, the Entity contains a natural language concatenation of the options (like Desk Lamp, Ceiling Lights and Outdoor Lights)
Expected Behavior
It should be possible to get the list of matched entities without accessing the native interpretation.
Proposed Solution
Ideally, the type EntityMap would allow for lists of entities
Amazon Lex V2, Alexa and potentially some other NLU systems support multi-valued slots, which are - as the name suggests - slots that can have a list of values.
Instead of having to go into the native interpretation, it should be possible to access lists of entities directly.
Example:
Given the phrase "Turn on {Lights}" with the slot Lights being multi valued, the utterance "Turn on the Desk Lamp, the Ceiling Lights and the Outdoor Lights" would match Lights as being
["Desk Lamp", "Ceiling Lights", "Outdoor Lights"]
Current Behavior
The only way to get the list of matched entities is to use
jovo.$entities[entityName].native
.When multiple values are matched through Lex, the
Entity
contains a natural language concatenation of the options (likeDesk Lamp, Ceiling Lights and Outdoor Lights
)Expected Behavior
It should be possible to get the list of matched entities without accessing the native interpretation.
Proposed Solution
Ideally, the type
EntityMap
would allow for lists of entitiesHowever, this would be a breaking change.
A non-breaking, alternative way to achieve this could be the following:
The text was updated successfully, but these errors were encountered: