Allow destructuring from screen with prefer-screen-queries

It would be great if prefer-screen-queries could allow destructuring from screen, for example:

it("renders foo", () => {
  const { getByText } = screen;

  render(<App />);

  // currently flagged by rule
  expect(getByText("foo")).toBeTruthy();
});

or

const { getByText } = screen;

it("renders foo", () => {
  render(<App />);

  // currently flagged by rule
  expect(getByText("foo")).toBeTruthy();
});

[Belco90]

Having said that, I’m happy to update the rule description to cover why it won’t allow you to destructure queries from screen.

[gndelia]

from what I understand in kent c dodds post about using screen

The benefit of using screen is you no longer need to keep the render call destructure up-to-date as you add/remove the queries you need. You only need to type screen. and let your editor’s magic autocomplete take care of the rest.

as I see it, your second example should be triggered by the linter as “incorrect”, according to the rule.

The only allowed scenarios to query should be screen.{{query}} calls, being the only exception any queries related to within (as it changes the bounding of the queries). There, nothing is said about allowing destructuring or not, so I assume it should be allowed…