Avoid doing console.error

[satazor]

This is not really a bug, nor a feature request, so I haven't followed any of the templates.

It seems console.error is being used in several situations, e.g.:

sdk-javascript/src/event/cloudevent.ts

Line 170 in 6cd310c

console.error(e.errors);

.

In most scenarios, these console.error calls are unnecessary as errors will be thrown anyway, that should be handled by devs consuming this library. In other situations, errors aren't thrown, and these messages are useful. However, most devs are using custom loggers (like JSON loggers), and would like to be able to customize the logging behavior.

[lance]

Thanks @satazor for opening this issue. It actually looks like there are only two calls to console.error() - the one you pointed out, and this one

sdk-javascript/src/message/http/index.ts

Line 51 in 6cd310c

console.error(`Unknown spec version ${version}. Default to ${Version.V1}`);

I think probably the one you note is the only one that should be removed, as the one in src/messages/http is informational and an exception isn't thrown.

[satazor]

@lance 👍

For informal logs, please consider adding the ability to specify the logger (maybe with the same interface as console), so that we can override with custom loggers.

[github-actions]

This issue is stale because it has been open 30 days with no activity.