I have a small voice-only skill and would like to upgrade to use APL. <p dir="auto

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Question: How to add APL support in Azure Functions? about alexa.net.apl HOT 2 CLOSED

aalmada commented on June 26, 2024

Question: How to add APL support in Azure Functions?

from alexa.net.apl.

Comments (2)

aalmada commented on June 26, 2024 1

Hi @stoiveyp. Thank you so much for the answer.

Almost at the same time I found a very similar solution. Here it is for future reference:

[FunctionName("MyFunction")]
public static async Task<IActionResult> Run([HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", Route = null)]HttpRequest request, ILogger log)
{
    log.LogInformation("Received a request.");

    var payload = await request.ReadAsStringAsync();
    var skillRequest = JsonConvert.DeserializeObject<APLSkillRequest>(payload);

    return skillRequest.Request switch
    {
        LaunchRequest _ 
            => await HandleLaunchRequest(log),

        IntentRequest intent 
            => await HandleIntent(skillRequest, intent, log),

        _ => new OkObjectResult(ResponseBuilder.Empty())
    };
}

I'm now going to start really using APL. I'll let you know how it goes.

from alexa.net.apl.

stoiveyp commented on June 26, 2024

Hi @aalmada thanks for reaching out.

We've had this with the core library as well - the underlying issue seems to be that azure functions don't use Json.Net functionality to deserialize the objects, This causes us trouble as we rely on that to work. It isn't an issue for AWS Lambda as they do use Json.Net

If you put the req function signature back to HttpRequest req then you can do something like the following, which should work

string requestBody = new StreamReader(await req.Content.ReadAsStreamAsync()).ReadToEnd();
APLSkillRequest skillRequest = JsonConvert.DeserializeObject<APLSkillRequest>(requestBody);

Let me know if this helps

from alexa.net.apl.

Recommend Projects