Dropped support for createCachedSelector calls with multiple arguments? about re-reselect HOT 3 CLOSED

Hi @mrlubos,
until version v3.3.0, options had to be provided through an extra argument after keySelector:

createCachedSelector(
  // ...
)(
  keySelector, { options }
)

Version v3.4.0 introduced the possibility of providing a single keySelector for simple cases or a single options object (accepting a keySelector entry) to get full powers.

createCachedSelector(
  // ...
)(
  keySelector | { options }
)

From v4.0.0 this became the only way to call createCachedSelector.

This means that -in complex scenarios- instead of providing a keySelector and an options object you have to provide just an options object with a keySelector entry.

If you wanted to uniform your createCachedSelector calls, use always the options object.

createCachedSelector(
  // ...
)(
  {
    keySelector
  }
)

from re-reselect.

I came here precisely for that explanation! Thanks @toomuchdesign

Maybe it could be restated as "Dropped support for createCachedSelector(...)(arguments) calls with multiple arguments" or something like that? The original statement is very confusing.

from re-reselect.

Thank you for the explanation @toomuchdesign!

from re-reselect.