Closed flaviendelangle closed 2 years ago
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.
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.
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.
These are the results for the performance tests:
Test case | Unit | Min | Max | Median | Mean | σ |
---|---|---|---|---|---|---|
Filter 100k rows | ms | 240.1 | 477.5 | 316.3 | 328.26 | 85.624 |
Sort 100k rows | ms | 477.8 | 947.2 | 642 | 682.5 | 154.688 |
Select 100k rows | ms | 113 | 224.3 | 195 | 188.16 | 40.008 |
Deselect 100k rows | ms | 89.5 | 216.5 | 202.6 | 160.72 | 50.838 |
Generated by :no_entry_sign: dangerJS against 5e745688ca4327e17c63f5b5d519cd34ebe888af
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.
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.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
👋 The migration PR has been merged.
Please follow these steps to make sure that the contents are all updated. (Sorry for the inconvenience)
*.md
or demo files, you are likely to encounter conflict because all of them have been moved to the new folder.
2.1 revert the change on those markdown files you did
2.2 pull latest master from upstream (you should not see conflict)
2.3 make the changes again at docs/data/data-grid/*
yarn docs:api
docs/pages/x/api/data-grid/*
if your PR touches some of the componentsIf you are struggle with the steps above, feel free to tag @siriwatknp
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.
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.
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.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
@flaviendelangle Would all the /x/api/date-pickers/*
pages be included in this PR?
@siriwatknp they should yes
This pull request has conflicts, please resolve those before we can evaluate the pull request.
@alexfauquette concerning the references to DataGridPro
or x-data-grid-pro
in the api page, I removed some hardcoded values and synced the ApiPage
file with the core (I can't use it directly because we have the concept of slots which they do not document).
I finally found Why date-range-picker description was empty, it's a regexp problem
The current one /date-range-picker.*.json$/
is valid for files such as
The .
needs to be escaped and the lang tag must be restrained to 2 letters to avoid accepting "date-range-picker-day"
A solution can be /\/date-range-picker(-[a-z]{2})?\.json$/
A solution can be /\/date-range-picker(-[a-z]{2})?.json$/
Done
Closes #2398
Doc preview Codesandbox pro example
Changes
For the view types, I removed the duplicates and only kept the type with the name of the view component, not the ones with the name of the pickers (
clock
nottime
,calendar
notdate
,calendarOrClock
notdateTime
),ClockView
,TimePickerView
ClockPickerView
,DatePickerView
CalendarPickerView
,DateTimePickerView
CalendarOrClockPickerView
Removing
ClockPickerStandalone
and instead haveClockPicker
handle the controlled / uncontrolled pattern just like inCalendarPicker
[x] Add
root
slot forClockPicker
[x] Rename
PickersCalendar
intoDayPicker
PRs ready to be picked: