React Native Windows: value except only Date as object, onchange not triggered if unselect date
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- javascript, react-native, typescript
Rechercherichtung
Start in the Windows picker implementation, datetimepicker.windows.js, and trace how sharedPropsValidation handles value and how onChange is called when the selected date is cleared. The report names utils.js as the validation location; check its tests and the Windows picker tests first. Done means null or undefined can be used as the value and clearing a date fires onChange; the issue has gone 873 days without a comment.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Bug report
Summary
datetimepicker.windows.js
- I want to set
undefinedornullas date value but it is prevented by validation. If i comment that line eveything is working fine. - If unselect the date in the datepicker by clicking on the current selected date, the onChange Event is never fired. So i never know how the state of the picker is.
Reproducible sample code
<DateTimePicker
style={styles.datePicker}
value={null} // NOT POSSIBLE to set NULL
display="calendar"
firstDayOfWeek={1}
onChange={(event: DateTimePickerEvent, date?: Date) => {
// NOT FIRED if unselect the date
}}
onError={(arg: Error) => console.log('GKU Date Error', arg)}/>
Steps to reproduce
--
Describe what you expected to happen:
- Null as initial value should be allows
- Validation for value in utils.js should be removed because it is already checked. And if i remove the init validation (sharedPropsValidation) everything works fine:
export default function RNDateTimePickerQWE(
props: WindowsNativeProps,
): React.Node {
sharedPropsValidation({value: props?.value}); // **REMOVING THIS LINE FIXES THE ISSUE**
const localProps = {
dayOfWeekFormat: props.dayOfWeekFormat,
dateFormat: props.dateFormat,
firstDayOfWeek: props.firstDayOfWeek,
maxDate: props.maximumDate ? props.maximumDate.getTime() : undefined, // time in milliseconds
minDate: props.minimumDate ? props.minimumDate.getTime() : undefined, // time in milliseconds
onChange: props.onChange,
placeholderText: props.placeholderText,
selectedDate: props.value ? props.value.getTime() : undefined, // time in milliseconds
style: [styles.rnDatePicker, props.style],
};
...
Environment info
npx react-native info output:
System:
OS: Windows 10 10.0.22621
CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
Memory: 13.63 GB / 31.73 GB
Binaries:
Node:
version: 16.19.1
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 3.6.0
path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm:
version: 8.19.3
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions:
- 10.0.18362.0
- 10.0.19041.0
- 10.0.22000.0
- 10.0.22621.0
IDEs:
Android Studio: AI-222.4459.24.2221.10121639
Visual Studio:
- 17.5.33502.453 (Visual Studio Community 2022)
- 16.11.33423.256 (Visual Studio Community 2019)
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
react-native-windows:
installed: 0.72.7
wanted: 0.72.7
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
datetimepicker version: 4.5.0
React Native Windows
- Vorherrschende Sprache
- JavaScript
- Sterne
- 2.9k
- Forks
- 459
- Ø Merge
- 4 T. 16 Std.
- Gemergte PRs (30 T.)
- 5
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus react-native-datetimepicker/datetimepicker
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 58/100
react-native-datetimepicker/datetimepicker#1070 · 1 Kommentar ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 52/100
-
DateTimePickerAndroid.open() throws "Cannot read property" error on RN 0.78.3 new architectureOffen
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
react-native-datetimepicker/datetimepicker#1047 · 6 Kommentare ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 20/100
react-native-datetimepicker/datetimepicker#1046 · 1 Kommentar ·
Alle Issues in react-native-datetimepicker/datetimepicker
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Fei-Away/Codex-Dream-Skin#449 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
outline/outline#14489 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Claude Code plugin does not wire the edit-time Floor hookEvtl. vergeben @dgr8akki hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
Maintainer antworten meist innerhalb von 1 Tag
-
Administration: required plugin configuration field stays invalid after restoring its saved valueOffenneeds-triage Platform(Default)
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
Maintainer antworten meist innerhalb von 1 Tag