[Snyk] Upgrade reselect from 4.0.0 to 4.1.5

[ido-krupkin-zooz]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade reselect from 4.0.0 to 4.1.5.

 :information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

- The recommended version is **12 versions** ahead of your current version. - The recommended version was released **5 months ago**, on 2021-11-24.

Release notes

Package name: reselect

• 4.1.5 - 2021-11-24
  

  This release updates the TS types to correctly infer selector parameters when input selectors have undefined or null as a parameter type or have optional parameters, and exports the CreateSelectorFunction type to fix uses of createStructuredSelector.

  (The types fixes feel like playing whack-a-mole, but they keep getting better!

  What's Changed

  • Fix intersection of parameters that are undefined by @ markerikson in #556
  • Export CreateSelectorFunction to fix createStructuredSelector usage by @ markerikson in #557

  Full Changelog: v4.1.4...v4.1.5

    </li>
    <li>
      <b>4.1.4</b> - <a href="https://snyk.io/redirect/github/reduxjs/reselect/releases/tag/v4.1.4">2021-11-17</a></br><p>This release has (you guessed it) more fixes to the TS types: a change to parameter merging that fixes breakage with selectors and RTK Query's API state, a simplification of the <code>OutputSelectorFields</code> type to improve selector variable readability, another update to parameter merging to flag nested <code>never</code> fields as compile errors, and a fix to <code>createStructuredSelector</code> parameters to resolve a lib compilation problem.</p>

  Changelog

  More TS Fixes

  The parameter merging fixes in 4.1.3 tried to "unwrap/expand" the parameter types to make them more readable, such as showing intersected objects as {a, b, c} instead of {a} & {b} & {c}. This was done with a recursive expansion type. That turned out to break with the complex state types used by RTK Query. We've updated the type expansion to only be a single level instead, which fixes the compilation issue.

  The OutputSelectorFields type previously took two generics: the Combiner function, and a Result type. This led to extra values being shown in hover previews for selectors. By inferring Result = ReturnType<Combiner>, we were able to drop the second generic and cut down on the amount of types shown in previews.

  A user noted that intersected objects with top-level incompatible fields (like {a: string} & {a: number}) resulted in empty objects, but no compile error. We've updated the parameter merging to flag those as never and catch the problem at compile time. Deeper nested incompatible fields should already be caught by TS.

  The previous fix to createStructuredSelector missed a step in the spreading process, which has now been fixed.

  What's Changed

  • Switch package management to Yarn v3 by @ markerikson in #551
  • Fix parameter expansion and improve OutputSelector readability by @ markerikson in #552

  Full Changelog: v4.1.3...v4.1.4

    </li>
    <li>
      <b>4.1.3</b> - <a href="https://snyk.io/redirect/github/reduxjs/reselect/releases/tag/v4.1.3">2021-11-16</a></br><p>This release rewrites the TS type inference of input selector parameters for correctness, fixes inference of <code>createStructuredSelector</code> inputs, and fixes an issue with the <code>OutputSelectorFields</code> type not being exported.</p>

  Changelog

  Input Selector Parameter Inference Improvements

  Reselect's types have always been extremely tricky, because it involves passing multiple input selectors with potentially heterogeneous, and then nested function composition of multiple selectors. Additionally, the input selectors can be passed as individual arguments or a single array of input selectors.

  The 4.0.0 typedefs dealt with this by hand-writing dozens of overloads, which was absolutely impossible to maintain.

  In 4.1, we took advantage of TS's improved abilities to infer array/tuple types to consolidate the typedefs.

  One of the issues that happened as a result was that arguments at the same input parameter index were being "unioned" together, rather than "intersectioned". For example, in this complex selector:

  <div class="highlight highlight-source-ts position-relative overflow-auto" data-snippet-clipboard-copy-content=" const input1 = ( _: StateA, { testNumber }: { testNumber: number }, c: number, d: string ) => testNumber

  const input2 = ( _: StateA, { testString }: { testString: string }, c: number | string ) => testString

  const input3 = ( _: StateA, { testBoolean }: { testBoolean: boolean }, c: number | string, d: string ) => testBoolean

  const input4 = (_: StateA, { testString2 }: { testString2: string }) => testString2

  const testSelector = createSelector( input1, input2, input3, input4, (testNumber, testString, testBoolean) => testNumber + testString )">

    const input1 = (
  _: StateA,
  { testNumber }: { testNumber: number },
  c: number,
  d: string
  ) => testNumber
  
  const input2 = (
  _: StateA,
  { testString }: { testString: string },
  c: number | string
  ) => testString
  const input3 = (
  _: StateA,
  { testBoolean }: { testBoolean: boolean },
  c: number | string,
  d: string
  ) => testBoolean
  const input4 = (_: StateA, { testString2 }: { testString2: string }) =>
  testString2
  const testSelector = createSelector(
  input1,
  input2,
  input3,
  input4,
  (testNumber, testString, testBoolean) => testNumber + testString
  )