refactor(no-container): remove wrong use case

scenario

Author: thebinaryfelix

docs/rules/no-container.md

@@ -20,10 +20,6 @@ const { container: alias } = render(<Example />);
 const button = alias.querySelector('.btn-primary');
 ```
 
-```js
-const button = screen.container.querySelector('.btn-primary');
-```
-
 ```js
 const view = render(<Example />);
 const button = view.container.querySelector('.btn-primary');

lib/rules/no-container.ts

@@ -72,15 +72,14 @@ export default ESLintUtils.RuleCreator(getDocsUrl)({
         ) {
           if (isMemberExpression(innerNode)) {
             if (isIdentifier(innerNode.object)) {
-              const isScreen = innerNode.object.name === 'screen';
               const isContainerName = innerNode.object.name === containerName;
               const isRenderWrapper =
                 innerNode.object.name === renderWrapperName;
 
               hasPropertyContainer =
                 isIdentifier(innerNode.property) &&
                 innerNode.property.name === 'container' &&
-                (isScreen || isRenderWrapper);
+                isRenderWrapper;
 
               if (isContainerName || hasPropertyContainer) {
                 context.report({

tests/lib/rules/no-container.test.ts

@@ -81,16 +81,6 @@ ruleTester.run(RULE_NAME, rule, {
         },
       ],
     },
-    {
-      code: `
-        const button = screen.container.querySelector('.btn-primary')
-      `,
-      errors: [
-        {
-          messageId: 'noContainer',
-        },
-      ],
-    },
     {
       code: `
         const view = render(<Example />)