Should we auto parse json trigger inputs or leave as string #21
Description
By default, we try to parse trigger inputs (for example, a queue/event hub/service bus message) as if they were JSON and leave them as a string if that fails. However, that can occasionally lead to weird behavior. For example, in this "copy blob" example it takes a blob input and copies it to a blob output. If the blob being copied is a json file, it will lose all formatting after it's copied because we parsed and serialized it instead of just leaving it as a string throughout the transaction.
Fwiw, it appears C# functions leaves these as strings, so we're also inconsistent across languages.
We could always make this a toggle-able option, but now would be a good time to decide if we want to change the default as a part of the v4 breaking change release.