Siyavash Habashi
Siyavash Habashi
Could we re-open this feature-request, having the same issue, or maybe a explanation why this is not do-able?
Please don't stale, trying to find some time trying to handle this issue.
> @janjaali if you want to add this, then look here: https://github.com/sksamuel/avro4s/blob/release/4.0.x/avro4s-core/src/main/scala/com/sksamuel/avro4s/Records.scala#L200-L205 > > You need to update that first case statement to look for an annotation on the field....
You need to setup the "Alexa Skill Kit" with you Skill ID as a trigger for your lambda in the AWS-console where you have configured your lambda.
No, the skill ID identifies your Skill against AWS Lambda. You may find the following link helpful: https://peterdaugaardrasmussen.com/2018/07/24/alexa-error-when-not-selecting-correct-blueprint/
I just tried to resolve the issue and improve the extensibility of the Map format . It would be kind if you would take a look at it :)
Is there any possibility that this PR will be processed any further?
Anybody some spare time to have a look at this one?
So, if I get you right, you are suggesting to drop the implicit status from the existing signature (did so in the PR) and remain with the new signature? As...
Handled in #40.