stoiveyp / alexa.net.annotations Goto Github PK

AlexaSkillPipeline takes an optional context argument that is available to handlers

This should be available as a boolean option on the AlexaSklill generator attribute

Instead of the request type, a handler method should be allowed to ask for the information object passed directly into the handler, if it's required (for example - to gain access to the items dictionary

Interceptor attribute should generate an interceptor in the same way the handler code does

When a handler method asks for the typed skill, it can also add an argument of type SkillRequest to the signature, and the handler will add it in as appropriate

Attribute attached to a method should run an analyzer to ensure the method signature is valid

For an intent attribute method - if type isn't request based, assume slot value and do lookup to directly pass in value via helper method

Interceptor methods should be able to filter execution based on request type

e.g. The method has an IntentRequest parameter - so the generated class has an if statement that executes the method only if it's that kind of request, allowing intent logging

Extend interceptor ArgumentFactory methods to perform these checks and generate the necessary if statements.
Implement Condition property in Interceptor argument detail returned by ArgumentFactory

Examples of what each attribute does and how it works

Current generator relies on SkillRequest - APLSkillRequest is required if you want to enable visuals properly (pay attention to device information)

SkillRequest should be the default - but a sub-type should be possible as an attribute on the AlexaSkill attribute, and if implemented - this should affect the method analyzers.

Currently only the isolated type names are checked when performing argument mapping and conversion.

This is assuming usings are being added by the user - limiting code generation. Ideally this should check type usage to include full namespace referencing, partial referencing and no referencing.

Note: Check to see if this is simplified by Semantic model?

If generated files are based on a class that uses a file level namespace - then this needs to be found and applied appropriately to ensure the partial class works correctly.