Bug: IntentResolution.data property not supported by addIntentListener callback

[rikoe]

The IntentResolution type returned by raiseIntent is defined as follows:

interface IntentResolution {
  source: string;
  data?: object;
  version: string;
}

but the addIntentListener callback is defined as follows:

addIntentListener(intent: string, handler: (context: Context) => void): Listener;

which includes no way to return data back to the caller. It is therefore impossible to populate the data property with the 1.0 API, causing an API inconsistency.

There are three options:

1. Document and leave the inconsistency as is.
2. Remove the data property from the IntentResolution interface until it can be provided.
3. Amend the addIntentListener interface to include a way to pass data back to the caller.

[nkolba]

my vote would be for #3 - Amend the addIntentListener interface to include a way to pass data back to the caller.

[rikoe]

I would like to propose that we leave the discrepancy with the data property, and the concept of returning results from intents alone for the 1.2 release.

There is a lot going into the 1.2 release already, and I feel like we need to tackle this topic properly subsequent to the 1.2 release.

Things to consider are:

• Better context type information about return types, and potentially strongly typing return data.
• Adding information about return types as part of intent registration in the app directory, similar to outgoing context types.
• Dealing with multiple return values for the same intent (Intent Listener callback signature provides no means to return a value #155).

[rikoe]

Close in favour of #201