The format is not applied in the range edition fields, nor are states updated

[JohabarWil]

Hi,

Version 0.11.10 is being used when implementing react-native-paper-dates in range mode, when entering to edit dates manually, the format is not applied, nor is the status of the entered dates updated

It was expected that when entering the dates in each field, the defined format would be applied, at the same time the status of the dates to save would be updated

NOTE: This was going to happen after migrating version of react-native-paper-dates from 0.9.2 to 0.11.10 (using react-native-paper V5.1.2)

Plays on iOS 12 and 16, Android 12,

configuration example

<DatePickerModal
locale={'en'}
mode="range"
visible={openPicker}
onDismiss={onDismiss}
startDate={range.startDate}
endDate={range.endDate}
onConfirm={confirmDate}
disableStatusBar={Platform.OS !== 'ios'}
validRange={{
startDate: new Date(clientCreationDate),
endDate: new Date(),
}}
uppercase={false} // optional, default is true
dateMode={'start'}
/>

Can someone help me? something you are doing wrong?

[iM-GeeKy]

PRs welcome!

[github-actions]

Hey! Thanks for opening the issue. Can you provide more information about the issue? Please fill the issue template when opening the issue without deleting any section. We need all the information we can, to be able to help. Make sure to at least provide - Current behaviour, Expected behaviour, A way to reproduce the issue with minimal code (link to snack.expo.dev) or a repo on GitHub, and the information about your environment (such as the platform of the device, versions of all the packages etc.).

[github-actions]

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.