[pickers] Do not support unparsed date formats anymore
Closes #5759
These are the results for the performance tests:
| Test case | Unit | Min | Max | Median | Mean | σ |
|---|---|---|---|---|---|---|
| Filter 100k rows | ms | 548.7 | 932.9 | 814.7 | 744.14 | 148.378 |
| Sort 100k rows | ms | 625.6 | 1,006.6 | 746 | 869.9 | 155.38 |
| Select 100k rows | ms | 179.1 | 272.4 | 206.9 | 219.82 | 32.87 |
| Deselect 100k rows | ms | 140.6 | 283.5 | 197.4 | 218.08 | 54.098 |
Generated by :no_entry_sign: dangerJS against 5b0aae22f1c42b5b6d21bdca80a89c22bae36647
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
I read some files, but it would take an eternity to open each file modification to check if modification are just type renaming or logic modification.
[...document.querySelectorAll('button.load-diff-button')].forEach(button => button.click());
🙈 😆
This pull request has conflicts, please resolve those before we can evaluate the pull request.
I read some files, but it would take an eternity to open each file modification to check if modification are just type renaming or logic modification. Are there some specific lines on which you have a doubt?
The internals mostly, the main point of risk for me is in usePickerState and the shared.ts (for each picker family)
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.