You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if no content-type is not provided, the receiver will just assume that it's receiving a Buffer. This limits the usefulness of the automatic parsing when dealing with legacy code as the receiver then basically always has to specify {contentType: 'application/json'}.
Instead of this manual step for unknown content types, it would be better for @cisl/io to try and guess the content type if it's not provided by doing something like:
Right now, if no content-type is not provided, the receiver will just assume that it's receiving a Buffer. This limits the usefulness of the automatic parsing when dealing with legacy code as the receiver then basically always has to specify
{contentType: 'application/json'}
.Instead of this manual step for unknown content types, it would be better for
@cisl/io
to try and guess the content type if it's not provided by doing something like:The text was updated successfully, but these errors were encountered: