Closed barbeau closed 8 years ago
To the best of my knowledge, the SDK would allow only one intent to enjoy the "single-word" status. For example, we can have an utterance entry like SetCityIntent {cityName}
but then we would not be able to have SetStopId {stopId}
since then Alexa won't be able to distinguish between them. (Unless she distinguishes by type of variable.)
I'm not sure what changed, but it seems to recognize when I just say "Tampa" now.
@philipmw Could you please give this a try as well to confirm? If it works we can close out this issue.
I went through UX bootstrap again today and it recognized "Tampa", so I'm going to close this. If we see otherwise we can reopen.
Looks like this is a problem again, but this time it's mapping single word city answers to the GetArrivalsIntent
. Adding SetCityIntent {cityName}
to utterances seems to fix this - will push a fix shortly.
This still doesn't work for "Atlanta" - I'm assuming because the three syllables are too close to some of the GetArrivalsIntent
utterances. If I remove some of those, it seems to work fine. Will push fix shortly.
Currently the skill asks "What is your city?". My response was "Seattle".
This doesn't currently work, as the skill currently requires the below type of utterances:
@philipmw is it possible to support single-word answers like this (e.g., just
SetCityIntent {cityName}
), or does it need to be mentioned in context of other words in an utterance?