chore: remove axios#1187
Conversation
| const fileName = name ?? data.name | ||
| const contentType = data.type | ||
| const fileOptions = { contentType, ...options } | ||
| const fileOptions = { ...options, contentType } |
There was a problem hiding this comment.
Why is this change needed? Just curious.
There was a problem hiding this comment.
seems like Claude's sidequest:
The old order let options override contentType, meaning if a caller explicitly passed a contentType in options, it would silently win over the file's own data.type. The new order makes the file's actual MIME type take precedence, which is the correct behavior — when you have a File object, its .type should not be overridable by the caller.
I'm not sure if it breaks anything, should I revert this change?
There was a problem hiding this comment.
Ok, we can keep it, thanks
| { | ||
| "name": "@ethersphere/bee-js", | ||
| "version": "12.2.2", | ||
| "name": "@upcoming/bee-js", |
|
@slapec93 I see that |
|
|
No description provided.