How to avoid default undefined parameters in various components?

[psk-dreampay]

I just upgrade the react native paper version to 5.0.1. Everything else seems fine but how can I avoid some compulsory parameters where the value of these parameters can be undefined. To give more details when working checkbox the following code was working properly before this update:

<Checkbox.Android status={status} onPress={onPress} disabled={disabled} testID={testID} theme={theme} uncheckedColor={uncheckedColor} color={color} />

But after the update I have to pass some additional parameters as follows:

<Checkbox.Android status={status} onPress={onPress} disabled={disabled} testID={testID} theme={theme} uncheckedColor={uncheckedColor} color={color} // new params accessibilityLabelledBy={undefined} accessibilityLanguage={undefined} onPointerEnter={undefined} onPointerEnterCapture={undefined} onPointerLeave={undefined} onPointerLeaveCapture={undefined} onPointerMove={undefined} onPointerMoveCapture={undefined} onPointerCancel={undefined} onPointerCancelCapture={undefined} onPointerDown={undefined} onPointerDownCapture={undefined} onPointerUp={undefined} onPointerUpCapture={undefined} onHoverIn={undefined} onHoverOut={undefined} delayHoverIn={undefined} delayHoverOut={undefined} />
Anything we can do here to just skip this parameters. This is happening with other components as well like
Fab, HelperText, IconButton, RadioButton, TextInput, AppBar.BackAction and TextInput.Icon.

[lukewalczak]

Please check if adding @types/[email protected] will solve your issue.

[psk-dreampay]

It's working now thanks a lot @lukewalczak

[elilabes]

@lukewalczak I have tried installing @types/[email protected] and the current release @types/[email protected]. Neither version fixes this issue for me. It started for me after upgrading from 5.0.0-rc9 to 5.1.3.

For me it is accessibilityLabelledBy and accessibilityLanguage that are required for every react-native-paper component

Any ideas? :)

[raajnadar]

@elilabes did you try deleting & regenerating the lock (yarn.lock or package.lock) file?

[elilabes]

@raajnadar yes - same issue

[warrenfalk]

I am also seeing this issue: react-native-paper@^5.1.3, @types/[email protected] (also occurs with 0.71.0)

The issue is that react-native-paper/lib/typescript/components/TextInput/TextInput.d.ts does a Pick<> on import("react-native").TextInputProps with "accessibilityLabelledBy" and "accessibilityLanguage" which do not exist on that type

[warrenfalk]

It looks like these two properties were only merged into the react-native typescript definitions a few hours ago facebook/react-native#35883 and facebook/react-native#35883

I'm not sure how react-native-paper already had them before react-native did, nor why a search in react-native-paper github does not find these in the code.

[DimitarNestorov]

@warrenfalk @elilabes 5.1.4 was just released. Can you try updating and let us know if you have any issues?

[warrenfalk]

After updating to 5.1.4, I no longer see the issue 👍️🙏

[elilabes]

Working now! Thanks @DimitarNestorov