You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating Custom Tasks for Alexa requires a tasks folder at platforms\alexaSkill\skill-package\tasks that contains task definition files. Calling --clean should not remove that folder or should make a backup copy first in a .clean folder.
Current Behavior
Calling $ jovo build --clean deletes the entire folder and the tasks contains task definition files that don't exist anyplace else so they can be lost.
Error log
None
Your Environment
Jovo CLI version used: 3.0.21
Operating System: Windows 10
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion. Although I understand where you're coming from, I think introducing a feature like this would be inconsistent behavior as the --clean flag should always delete the complete folder and create it with completely fresh content.
As a workaround, would it make sense to store your custom tasks in a separate folder outside the platforms folder and copy them into the folder (e.g. with a script) after running jovo build?
The more I think about it, I like the idea of creating a backup folder and every time --clean is run a new folder based on datetime is created and the old folder is copied into it. Then the delete of the folder happens.
I just know that Amazon is putting more things in the platforms\alexaSkill\skill-package folder. So, maybe the skill.json file should be the only one deleted from there.
I'm submitting a...
Expected Behavior
Creating Custom Tasks for Alexa requires a
tasks
folder atplatforms\alexaSkill\skill-package\tasks
that contains task definition files. Calling --clean should not remove that folder or should make a backup copy first in a.clean
folder.Current Behavior
Calling
$ jovo build --clean
deletes the entire folder and thetasks
contains task definition files that don't exist anyplace else so they can be lost.Error log
None
Your Environment
The text was updated successfully, but these errors were encountered: