Compatibility with eslint-plugin-testing-library

Describe the Feature

It would be lovely to verify that our library is compatible with eslint-plugin-testing-library, determine what’s missing and plan the necessary work to make it usable.

Possible Implementations

I’d like avoid creating another plugin based on the existing one. I’d prefer documenting the shortcomings (e.g. lack of screen if there are rules for that)

[thymikee]

• prefer-screen-queries. This will require having a screen object.

Only this one is relevant now, since we don’t have screen queries.

[cross19xx]

With the exception of the following syntaxes, all other rules are valid and compatible with eslint-plugin-testing-library.

• no-debug: Using the default debug is seen as a valid syntax, whereas using the debug inside the render method is seen as an invalid syntax, i.e.

  // Valid syntax
  import {debug} from 'react-native-testing-library';
  debug(<Component />);
  
  // Invalid syntax
  import {render} from 'react-native-testing-library';
  const {debug} = render(<Component />);
  

  Luckily, react-native-testing-library@next covers this.

• prefer-wait-for: This is shown as an invalid syntax the wait method in RNTL is waitForElement. A suggestion will be to have an alias for waitForElement as waitFor. Depending on the state of this (i.e. if on or off), no-wait-for-empty-callback may be triggered

• prefer-screen-queries. This will require having a screen object.