Not sure this is absolutely necessary, but it prevents people from rapidly reordering things so quickly that stale indices are used.

fix: block rapid reordering from using stale indices

…ivecar#32)

On android, when dragging, the item is placed around 50px below the touch point.
The reason is that: we use the measureInWindow which does not really return screencoordinate.
---------

Co-authored-by: golery <golery.team@gmail.com>
Co-authored-by: Philip Su <39933441+fivecar@users.noreply.github.com>

…vecar#37)

This reverts commit cfa973c, which began to cause warnings and issues in React Native (because function components can't take a ref).

We then update how we handle the refs in Typescript so that there are no Typescript errors when you use the component.

We now support them.

This implements the suggested change in fivecar#38 . It fixes the `measure` parameters. An already existing example of the correct parameters can be seen in the const onDragLayout.

React Native docs say Android needs this experimental flag to be on if you use LayoutAnimation, but we don't. It had been causing some crashes, so here's the fix.

* add index to keyExtractor
* update readme

---------

Co-authored-by: Alice <alice@ritsu.dev>