Google Actions: AMAZON.YesIntent is invalid

[asarazan]

I believe the jovo-cli on dialogflow used to take care of normalizing these intents into just YesIntent etc. I'm now rolling my own CLI by utilizing jovo-model.

I'm not sure if that falls within the scope of this library or if that's something I should be handling in my own code. Would love some clarity!

[jankoenig]

Hey! Could you paste the relevant part of your model JSON? Is the AMAZON.YesIntent in the alexa section?

[asarazan]

Ah yeah, they're definitely in the common area. Just realized there was a different layer of our stack that was responsible for normalizing these. Sadly only 1/3 of the issues I filed friday ended up being valid lol

[asarazan]

Actually, is it worth reopening to discuss whether jovo should attempt to mirror some of the naming restrictions in its various platforms? Here's the error I get if I try to manually enter a period in an intent name:

[asarazan]

I guess the use case we have is that we just use names like `AMAZON.YesIntent` in the common section of our model file. DialogFlow has always been happy with those names, even though it looks weird. There's an argument to be made that we should have just called it `YesIntent` with a platform override and that it's good that the platform is calling us out for it.

…

On Tue, Oct 13, 2020 at 11:45 PM Alex ***@***.***> wrote: Good question. Does it make sense to have periods in the intent name? Even Alexa doesn't support periods in custom intents. Not sure if it would break existing voice apps — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEERGAH7PI3J3USMSFPQZDSKVCILANCNFSM4SCBOUJA> .