-
Notifications
You must be signed in to change notification settings - Fork 15
Fix handling of nested paths #56
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
Fix handling of nested paths #56
Conversation
|
@aditbiswas1 how does it look like with the MR? I kinda need this to be merged. |
|
@aditbiswas1 we need one more to merge it, could you pls find someone? |
| // expectations | ||
| expect(value.userId).toEqual(userId); | ||
| expect(value.auth.authToken).toEqual(authToken); | ||
| expect(value.auth.key).toEqual(key); |
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.
how is this test of auth.key any different from auth.authToken ?
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.
With the current version of the library this would fail since there is no deep merge.
| // expectations | ||
| expect(value.userId).toEqual(userId); | ||
| expect(value.auth.authToken).toEqual(authToken); | ||
| expect(value.auth.key).toEqual(key); |
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.
With the current version of the library this would fail since there is no deep merge.
Fixes handling of nested paths at the cost of adding a dependency on Lodash.