[BUG] Type for onRemove seems to be incorrect

[floatplane]

Describe the bug
As far as I can tell, onRemove is always called with a single item, yet it's declared to accept multiple items:

react-native-select-pro/packages/react-native-select-pro/src/types/types.ts

Lines 207 to 214 in 6bc7677

	/**
	* Callback that is called when option(s) is cleared
	*
	* @param option removed option(s)
	* @param optionIndex removed option(s) index(es)
	* @category Callback
	*/
	onRemove?: <T>(option: OptionType<T> | OptionType<T>[], optionIndex: number | number[]) => void;

Because of this, I get TypeScript errors in my code unless I convince the compiler that I know what I'm doing:

      <Select
        onRemove={(option) => {
          const removedValue = Array.isArray(option) ? option[0].value : option.value;
          // ... do something with removedValue
        }}

Notice that the example in the repo has to actively suppress this error with as OptionType:

react-native-select-pro/apps/expo/src/examples/real-example.tsx

Lines 51 to 57 in 6bc7677

	onRemove={(option) => {
	field.onChange(
	field.value.filter(
	(item) => item.value !== (option as OptionType).value,
	),
	);
	}}

To Reproduce
Steps to reproduce the behavior:

1. Set up a TypeScript app
2. Add an onRemove handler
3. See compile error

Expected behavior
No compile errors in code like this:

const Foo = () => (
  <Select
    multiple
    options={[
      {label: 'One', value: '1'},
      {label: 'two', value: '2'},
      {label: 'Three', value: '3'},
    ]}
    onSelect={
      ({value}, optionIndex) => {
        console.log(`Selected ${value} which is the ${optionIndex}th item`)
      }
    }
    onRemove={
      ({value}, optionIndex) => {
        console.log(`Removed ${value} which is the ${optionIndex}th item`)
      }
    }
  />
);

Screenshots

Environment (please complete the following information):

• OS: any
• OS Version: any

[irekrog]

Hi @floatplane , thanks for reporting, and you can use the latest version 2.1.1

[floatplane]

thanks for the quick fix @irekrog! really appreciate it 😄