Error with new trigger: panic: index out of range about flogo-contrib

[Adirio]

Update: removing the payload output both in the trigger.go and trigger.json so it seems it has some problem with the [X]uint8 array. How should I pass the payload then? Or how should I specify it is an array in the trigger.json file?

[Adirio]

Update: Setting it to "array" in the .json file seems to have solved the problem but wasn't able to find any documentation nor the part of the code where this assertion is being made. Pointers to any of those two parts would be welcome.

[fm-tibco]

I'll look into the "index out of range" and output not showing. At a minimum try to give a more constructive error to help diagnose the problem.

Also, we are working on cleaning put and adding additional documentation. Please create a documentation issue which we can address separately. Thank you.

[Adirio]

I tracked the error as much as I could but wasn't able to find more. Using "type": "bytearray" in the trigger.json file was yielding the error while "type": "array" isn't. Is there any kind of parsing being done depending on this config parameter? If the answer is yes, ¿what types am I able to use? I thought this was just some kind of meta config information that the trigger could use to parse it but that wasn't being used by the engine itself.

[fm-tibco]

Yes, the issue is that we currently do not have an explicit bytearray type. The types that you can use can be found in our flogo types go file.

We'll have to create a separate issue for type validation so you don't get this obscure errors.