generated from fastify/skeleton
-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The reason behind the all
option
#28
Comments
The typescript typings are recursively determining the final object shape and thus can slow down your typescript transpilation and your IDE, like vscode. |
Oh yes. I forgot about the typescript typing. Is Meanwhile I think we should state clearly in the doc. The current description is too vague about this option. |
You can provide a PR if you like. |
Merged
4 tasks
4 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Prerequisites
Issue
I'm curious about the purpose of the
all
option. From the code, it appears that_deepmergeAll
is the same as_deepmerge
when two arguments are present, but can also be used for other n-argument cases. Could we use_deepmergeAll
as the default option? Have I overlooked something?The text was updated successfully, but these errors were encountered: