style: update types to handle ref attributes

[leezumstein]

Context

Updating the types for FlatGrid and SectionGrid so we can leverage the ref attribute for the underlying SectionList and FlatList. This allows the consumer to do something like the following:

import * as React from 'react'

import { FlatList, Text } from 'react-native'
import { FlatGrid } from 'react-native-super-grid'

const DATA = [1, 2, 3, 4]

const MyComponent: React.FC = () => {
  const ref = React.useRef<FlatList<number>>(null)

  const onLayout = useCallback(() => {
    if (ref.current == null) return

    ref.current.scrollToEnd({ animated: true })
  }, [])

  return (
    <FlatGrid
      ref={ref}
      onLayout={onLayout}
      itemDimension={100}
      data={DATA}
      renderItem={({ item }) => <Text>{item}</Text>}
    />
  )
}

Without these changes, the components are typed with the ref attribute as FlatGrid<number>, which doesn't expose any of the methods defined by FlatList.

Image of the typing errors we were running into our project with the current implementation:

Image of the updated types being inferred after these changes are made:

Changes

• [x] Update FlatGrid and SectionGrid types to be Functional Components with ref attributes inherited from FlatList and SectionList
  • This is stealing the types used by React.forwardRef essentially, which is what is used by the code implementation, anyways

[saleel]

Sorry for the delay. Merged and released v4.4.3

[leezumstein]

Sorry for the delay. Merged and released v4.4.3

No worries, thanks for taking a look + releasing!

[leezumstein]

@saleel I just checked and it looks like v4.4.3 hasn't landed on npm just yet. Wasn't sure if an action wasn't kicked off for the new version to publish it?

[saleel]

@leezumstein It was my mistake. I forgot to publish and only pushed to master instead. Published now - 4.4.3

[leezumstein]

@leezumstein It was my mistake. I forgot to publish and only pushed to master instead. Published now - 4.4.3

Yup I see it now, thanks again!