JS documentation is insufficient.

[dailytabs]

samples/javascript/UsersTrigger/index.js

What is context? What is event? Why is the event a string? Events have key, value, timestamp, etc... This makes no sense. Why is there no actual documentation for the code you have provided? The README just tells us how to run the container and does nothing to actually explain how to use this!

KafkaJS has consumer like:

await consumer.run({
    eachMessage: async ({ topic, partition, message }) => {
        console.log({
            key: message.key.toString(),
            value: JSON.parse(message.value.toString()),
            headers: message.headers,
        })
    },
})

where event is an object containing the properties of the event.

And producer like:

await producer.send({
    topic: 'topic-name',
    messages: [
        { key: 'key1', value: 'hello world', partition: 0 },
        { key: 'key2', value: 'hey hey!', partition: 1 }
    ],
})

How is your trigger/consumer interface in any way compatible with consuming these?

Kafka messages can be serialized in multiple formats. Currently the following formats are supported: string, Avro and Protobuf.

Why are binary messages not supported? Isn't this the default/de-facto format for Kafka messages?!? I seriously have to take my binary data, turn it into JSON or some string format before producing, then decode it on the consumer, when Kafka deals with binary internally. This sounds ridiculously wasteful!

[dailytabs]

UsersTriggerMany uses "string", UsersTrigger uses "binary" (which, according to docs, isn't supported) - yet, they both process the event as a string. This makes no sense.

Also, where is the list of values to use for dataType in the binding? The main README only mentions it with Java and it only has binary and string, no avro or protobuff. So many holes...

[shrohilla]

@dailytabs , we have updated the documentation. Would request you to please check them once again and share your feedback.
It's on github as well as on Microsoft public documentation

[shrohilla]

@dailytabs , we have updated the documentation. Would request you to please check them once again and share your feedback.
It's on github as well as on Microsoft public documentation