Complex 'slots' (entities) returned from Dialogflow use 'key' property? about jovo-cli HOT 3 CLOSED

Hi @peternann,

The value is the original input value (what the user said), and the key is the value of the entity it is being resolved to. This is mostly useful when synonyms are used for entities/slots, and to be honest, I haven't used multi-property entities before, so any feedback on how to solve this better is appreciated.

Here's a short explanation of the input object, however you're correct that we could do a better job explaining it: https://www.jovo.tech/framework/docs/data#how-to-access-input. The id is necessary for cross-platform compatibility with Alexa.

What exactly of the format of key do you think is weird? Maybe I'm missing something, but isn't it exactly the values you pasted at the bottom?

from jovo-cli.

I guess all I'm really saying is that the contents doesn't look like a 'key'. Seems to be a strange name for an object containing multiple key-value pairs.
Does the name 'key' have something to do with Alexa Intents perhaps?

It works though - If you document it, I'll use it!
Doco would be something like:

• For Dialogflow 'Entities' that return a multi-property 'object' (such as @sys.location), the filled object will appear in the 'key' property, and the full text for the matched Entity will appear in 'value'. - For complex entity cases, the 'value' is generally less useful than the broken-down detail in the 'key' object.

from jovo-cli.

Closing this due to inactivity.

from jovo-cli.