Skip to content

Support resolving underlying @jest/globals method from import #1106

Closed

Description

While we now support @jest/globals via #1094, we currently are still doing our checks against the "local name" of whatever is being imported, e.g.

import { xit as it } from '@jest/globals';

it('is skipped', () => {
  //
});

For the above rules see this as importing it rather than xit - we're already resolving this information as part of our reference scope checking, we just need to expose it.

This will make the API a bit more cumbersome, because we have to change from a boolean type guard check to an "extract" based method (similar to parseExpectCall) but I think it's worth it.

This is required for #1101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions