-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dep(): populateWithProperties
=> pick
#8202
Conversation
Code Coverage Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
READY
no leave the util folder aloneeeee i m working on that |
OK |
the pr is good do it when i l done there. I have 2 files left |
The old populateWithProperties was mutating objects that were created to be returned. |
The typing for pick is a bit too strict, as it is toObject. |
objects: this._objects | ||
.filter((object) => !object.excludeFromExport) | ||
.map((instance) => this._toObject(instance, methodName, propertiesToInclude)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure this is an improvement whatsover. is a bit harsh to read
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ll open a task to revert the strict typing.
I don't understand your comment regarding the typing of pick. |
Co-authored-by: Andrea Bogazzi <andreabogazzi79@gmail.com>
signature changed
pick(source, keys) => new object