chore: merge iteration of Sep. #486
Triggered via pull request
September 23, 2024 07:09
Status
Success
Total duration
3m 44s
Artifacts
–
Annotations
11 warnings
changed
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
changed:
components/date-picker/date-picker.tsx#L603
The autoFocus prop should not be used, as it can reduce usability and accessibility for users
|
changed:
components/date-picker/month-picker.tsx#L378
The autoFocus prop should not be used, as it can reduce usability and accessibility for users
|
changed:
components/date-picker/range-picker.tsx#L31
'PanelFooterProps' is defined but never used
|
changed:
components/date-picker/year-picker.tsx#L363
The autoFocus prop should not be used, as it can reduce usability and accessibility for users
|
changed:
components/tab/__docs__/demo/trigger-type/index.tsx#L1
'MouseEvent' is defined but never used
|
changed:
components/tab/tabs/nav.tsx#L401
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
changed:
components/tab/tabs/nav.tsx#L402
Non-interactive elements should not be assigned interactive roles
|
changed:
components/tab/tabs/nav.tsx#L686
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
changed:
components/tab/tabs/nav.tsx#L722
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
changed:
components/tab/tabs/nav.tsx#L722
Non-interactive elements should not be assigned mouse or keyboard event listeners
|