Calling Signal entity HTTP API fails with content-type=application/json

[timothyvries]

Context

In the http api documentation for signalling a durable entity it is stated that the request content (payload) should be JSON-formatted, implying that the Content-Type should be application/json.
Calling the API using this Content-Type=applicaton/json will throw an error in the get_input() function of the Durable entity context with the error "the JSON object must be str, bytes or bytearray, not dict"

How to reproduce

Call the API using Content-Type = application/json

Workaround

Call the API using Content-Type = text/plain

[davidmrdavid]

Thanks for reaching out @timothyvries, and I'm glad there's a clear workaround here. We'll be taking a look at this and prioritize this accordingly, thanks!