fix(typescript): missing generic parameter of React.RefObject

[fabb]

What:

Adds the generic type parameter for React.RefObject.

Why:
Fixes #1536
In @types/react, the type definition looks like this:

    interface RefObject<T> {
        readonly current: T | null;
    }

This means the T generic parameter needs to be set mandatorily.

In case skipLibCheck is not set to true, this causes a typescript type error:

../../node_modules/downshift/typings/index.d.ts:112:9 - error TS2314: Generic type 'RefObject<T>' requires 1 type argument(s).

112   ref?: React.RefObject
            ~~~~~~~~~~~~~~~

How:

I've added any as type parameter, which is not ideal but avoids adding a generic type parameter to the parent types (e.g. GetRootPropsOptions).

Open for better suggestions.

Checklist:

• Documentation N/A
• Tests N/A
• TypeScript Types
• Flow Types N/A
• Ready to be merged
  

[fabb]

related to #1521

[silviuaavram]

@fabb thank you for the changes.

Do you think that the original proposed suggestion would be better? The one from the mentioned issue.

export interface GetRootPropsOptions<E extends HTMLElement> {
  refKey?: string
  ref?: React.Ref<E>
}

[fabb]

Yes that would probably be better.

[silviuaavram]

The HTML element proposal will not work with React Native. I believe that having any at the moment is good enough to unblock us, and the overall types are already an improvement over the previous ones. If anyone can propose a better way with generics, we can change it later.

[github-actions]

🎉 This PR is included in version 8.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀