voxaai / voxa-generator Goto Github PK

The skill doesn't show any error messages by default or anything to guide users how to use the thing in the console. It should at least show on the console that it's running and listening to port 3000.

Add some sample utterances to the file speechAssets/SampleUtterances

we're actually moving away from eslint and more in the prettier direction

Make sure to create test for the actual generator http://yeoman.io/authoring/testing.html

We should add something like npm run start so developers can run the project easily. Also add this to readme and when the generator finishes

The current HelpIntent response reads

say: 'For Further details make sure to check Voxa Documentation at voxa.readthedocs.io',

Let's update it to

say: 'For Further details make sure to check Voxa Documentation at voxa.read the docs.io',

Which sounds a lot better

I new on this Voxa framework, I followed the steps mentioned in a medium post, but the interesting thing here is that I created the directory before using the generator.

Add to the readme how to execute voxa with debug enable. DEBUG=voxa

Voxa generate different intents/states from the one that are used on the speech assets folder(utterances/ intents).
Make sure to be the same intents in both sides.

No more needs for gulp, let's use plain nodemon and no more need for gulp.

We don't need to ask for a dependency installation this needs to be done automatically.

Once you generate a new project a bunch of error from eslint appears. Make sure the project is clean from eslint errors.

When you run the generator make sure to ask for a description.

Description should be included on package.json and README

For each file should be a reference to voxa functions so developers can get easily into it

Add more reference to Voxa on the template readme.md
At least where they can find documentation, samples, npm etc.

Explain to developers what they can do after they generate a new repo.
Which port runs, recomend to use ngrok ...

Maybe add curl command to test their Skill

Maybe add a reference to onSessionStarted, onSessionEnded, and onRequestStated. So developers know this handlers exits

Shoule be base on _.includes(). which function name should turn the NODE_ENV into production or development

if(_.includes(['skillNameProd'], functionName)) return 'production';

Add handlers for onError, onStateMachineError, onUnhandledState.

Add an error response for view. This response should be use on this handlers

Double check slot folder. When you try to generate it doesn't create the slot folder