Currently the behaviour of sync/async for HTTP and library triggers is different: one returns output with a failure and the other throws an exception. They should be consistent.
This should be updated after merging #173 and #201. We need a consistent interface for sync/async, and we need to handle properly success & failure returns.
Currently the behaviour of sync/async for HTTP and library triggers is different: one returns output with a failure and the other throws an exception. They should be consistent.
Same applies to new triggers (storage).