Wdyr ignores equality function in useSelector

[RobertGoins]

When using wdyr I noticed that it reports unnecessary renders caused by useSelector with an equality function even though the equality function causes the render to be avoided. Looking at the code it looks like wdyr does not consider the result of the equality function.

An example:

useSelector(someSelector, (prev, next) => true);

[vzaidman]

Good point.
useSelector is a custom hook, and as such, we only consider it's result.
How would you expect it to work?
I remind you that we only track custom hooks since you added them in the options, so probably we need to extend the options:

import React from 'react';

if (process.env.NODE_ENV === 'development') {
  const whyDidYouRender = require('@welldone-software/why-did-you-render');
  const ReactRedux = require('react-redux');
  whyDidYouRender(React, {
    trackAllPureComponents: true,
    trackExtraHooks: [
      [ReactRedux, 'useSelector']
    ]
  });
}

[DouglasPds]

I could not reproduce this error. When I used the example given by Robert (prev, next) => true, or using the shallowEqual of the Redux as equalityFn, the wdyr does not show the message of rerendering.

I don't know if I understand this error correctly.

[trickeyd]

I am getting this issue too, and it is making use of wdyr rather difficult to use unfortunately.

@RobertGoins - did you find a way round this?

@DouglasPds - when you tested, are you sure that you weren't also returning the same values? The hook will check for strict equality (===) before invoking the equality function.