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
I have searched existing issues to ensure the bug has not already been reported
Fastify version
"@fastify/deepmerge": "^2.0.1"
Plugin version
No response
Node.js version
20.x
Operating system
macOS
Operating system version (i.e. 20.04, 11.3, 10)
15.3
Description
deepmerge considers a File a mergable object (passes isMergeableObjecthere), which results in a busted output (an object containing just the path field).
Similar to how that code special cases RegExp and Date, should it special case File?
If not, should there be a way for the user to provide their own function to augment/replace this if they want the behaviour I do? (which is specifically for the source file to overwrite the target File during a merge).
Link to code that reproduces the bug
No response
Expected Behavior
No response
The text was updated successfully, but these errors were encountered:
#68 got merged. So you should be able to modify isMergeableObject as soon as the new version of deepmerge is released.
So you can pass a custom isMergeableObject and check for File Objects.
Prerequisites
Fastify version
"@fastify/deepmerge": "^2.0.1"
Plugin version
No response
Node.js version
20.x
Operating system
macOS
Operating system version (i.e. 20.04, 11.3, 10)
15.3
Description
deepmerge
considers aFile
a mergable object (passesisMergeableObject
here), which results in a busted output (an object containing just thepath
field).Similar to how that code special cases RegExp and Date, should it special case File?
If not, should there be a way for the user to provide their own function to augment/replace this if they want the behaviour I do? (which is specifically for the source file to overwrite the target File during a merge).
Link to code that reproduces the bug
No response
Expected Behavior
No response
The text was updated successfully, but these errors were encountered: