tejashah88 / node-alexa-smapi Goto Github PK

@tejashah88 do you have any thoughts on adding support for v1? I have made (private) changes to support v1 but not sure if it would be necessary to continue supporting v0 and how to tackle any backwards compatibility. Thoughts?

Please provive an as-small-as-possible, but complete and working sample. And show how or where to get refreshToken, clientId and clientSecret.

Thanks.

• Add unit and integration tests
  • Vendor operations
  • Skill operations
  • Interaction model operations
  • Account linking operations
  • Skill enablement operations
  • Skill testing operations
    • Validation
    • Invocation
    • Simulation
  • intent request history
  • Skill certification operations
  • node-alexa-smapi Custom operations
  • node-alexa-smapi helper methods
  • node-alexa-smapi error scenarios
• Add Travis CI integration
• Add coveralls.io integration

Hello,

The API Works fine, i can create and update skills and the interaction model.
But unfortunately i can't update icons.

i uploaded my new icon to Amazon S3. Made the URL Public. The Size are 108x108 & 512x512.
But if i try to update the icons, the update returns success, but the update is completly ignored.
Not only the update of the icons, also the update of other fields... if i comment out the icon stuff, the update is executed successfully, and the updates can be shown in the developer console.

`
var oTargetSkillManifest = await mySmapiClient.skills.getManifest(aConfigs[i].sSkillID, sStageDevelopment);
oTargetSkillManifest.manifest.publishingInformation.locales['de-DE'].name = sNewName;
oTargetSkillManifest.manifest.publishingInformation.locales['de-DE'].smallIconUri = sSmallIconUrl;
oTargetSkillManifest.manifest.publishingInformation.locales['de-DE'].largeIconUri = .sLargeIconUrl;
var oTargetSkill = await mySmapiClient.skills.update(aConfigs[i].sSkillID, sStageDevelopment, oTargetSkillManifest.manifest);

is it maybe an bug, or do i have to speficy/upload my images in a special way?

Kind Regards
Stefan
`

One of the issues that I can see while going forward is how to future-proof this library when new endpoints are being added. Currently we have the ability to make custom calls but that won't be enough as Amazon keeps on adding new endpoints.

One idea I have so far is an "API coverage" tool that scrapes the Alexa docs for request patterns and compares it to the internal library code and finally generates a table of endpoints that are not implemented yet. I've experimented with this in the node-meraki-dashboard library and aside from a few problems, it turned out to be quite successful.

The major problems as it seems is that:

1. The tool is highly dependent on the fact that the formatting of the Alexa docs will not change.
2. The library's code is a lot more complex and trying to analyze it directly would make more trouble than it's worth.
3. It's hard to reliably test the tool itself, due to the above problems.

These problems could make the tool quite brittle, but it would help in automating the process of checking for new endpoints every once in a while and manually adding them periodically.