-
Notifications
You must be signed in to change notification settings - Fork 4k
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(assertions): object partiality is dropped passing through arrays #18525
Conversation
`objectLike()` imposes partial object matching. That means that we don't need to fully specify all properties of an object to match it, but just the properties we care about (all other properties can have any value). Partial object matching is inherited. That means that in nested objects, the partiality is maintained: ```ts objectLike({ x: 'x', inner: { // Matches any object that has AT LEAST an 'y' property y: 'y', } }) ``` However, the partiality is dropped when passing through arrays: ```ts objectLike({ x: 'x', inner: [ { // Matches any object that has ONLY an 'y' property y: 'y', } ], }) ``` This is both unintuitive and different from past behavior, which makes migrating tests unnecessarily hard. Fix the discrepancy.
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.
Thanks!
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…ws#18525) `objectLike()` imposes partial object matching. That means that we don't need to fully specify all properties of an object to match it, but just the properties we care about (all other properties can have any value). Partial object matching is inherited. That means that in nested objects, the partiality is maintained: ```ts objectLike({ x: 'x', inner: { // Matches any object that has AT LEAST an 'y' property y: 'y', } }) ``` However, the partiality is dropped when passing through arrays: ```ts objectLike({ x: 'x', inner: [ { // Matches any object that has ONLY an 'y' property y: 'y', } ], }) ``` This is both unintuitive and different from past behavior, which makes migrating tests unnecessarily hard. Fix the discrepancy. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
objectLike()
imposes partial object matching. That means that we don'tneed to fully specify all properties of an object to match it, but
just the properties we care about (all other properties can have any
value).
Partial object matching is inherited. That means that in nested
objects, the partiality is maintained:
However, the partiality is dropped when passing through arrays:
This is both unintuitive and different from past behavior, which makes
migrating tests unnecessarily hard.
Fix the discrepancy.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license