-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Core: Ensure that context.args is always set
#16790
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
Conversation
Nx Cloud ReportCI ran the following commands for commit 35d0096. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
context.args is always set.context.args is always set
| hooks: new HooksContext(), | ||
| ...firstStory, | ||
| } as any); | ||
| expect(renderMock).toHaveBeenCalledWith({}, expect.objectContaining({ argsByTarget: {} })); |
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.
@tmeasday shouldn't this be asserting something about args? and same for above?
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.
Args is the first argument ({})
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.
aha! 💡
shilman
left a comment
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.
LGTM!
Issue: #16743
What I did
Ensure we don't filter all args down to nothing.
How to test
Yes see tests