Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[unbound-method]: don't report unbound methods passed to jest.mocked #1596

Open
FloEdelmann opened this issue May 29, 2024 · 0 comments · May be fixed by #1681
Open

[unbound-method]: don't report unbound methods passed to jest.mocked #1596

FloEdelmann opened this issue May 29, 2024 · 0 comments · May be fixed by #1681
Labels
enhancement

Comments

@FloEdelmann
Copy link
Contributor 

import foo from './foo'

jest.mock('./foo')

jest.mocked(foo.bar).mockResolvedValue(baz)
//          ^^^^^^^ jest/unbound-method reports an error here

expect(foo.bar).toHaveBeenCalled() // no error here

Since jest.mocked will be called with mock functions, it should not make a difference whether it is bound or not, right? So I'd suggest to not report an error for unbound methods passed to jest.mocked, just like already happens when passing it to expect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(unbound-methods): ignore functions passed to jest.mocked FloEdelmann/eslint-plugin-jest
2 participants
@FloEdelmann @G-Rath