[react/destructuring-assignment] Shows weird behaviour when I declare a variable with the name context

[roman-16]

In a functional component I get an error when I declare a variable with the name context.
Example code:

const Test = props => {
  const context = useContext(someContext);

  return (
    <div {...props}>
      {context.test} // Here message: 'Must use destructuring context'
    </div>
  );
}

[ljharb]

The error here should appear imo with any variable name coming from the useContext hook. Does the error disappear if you use a different variable name?

[roman-16]

No, then it doesn't appear.

[ljharb]

There seems like two bugs then:

1. the variable name context shouldn't be special
2. the return of useContext should be caught by this rule with every var name (altho this might need an option)

[ed-jinyoung-park]

I think the error message on that case is correct following this rule, isn't it?
can you explain more why there is a bug ?

[ljharb]

@Zinyon the rule is supposed to enforce legacy context being destructured; it's not supposed to warn on useContext, or on any variable that happens to be named context.

[ed-jinyoung-park]

@ljharb Thank you, it makes sense! and I'll try fix this.