Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add aria required prop to slider #1051

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

DSoliz
Copy link

@DSoliz DSoliz commented Nov 20, 2024

What the PR does

Add the aria-required prop to slider

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-required

Summary by CodeRabbit

  • 新功能
    • Slider 组件中添加了 ariaRequired 属性,增强了可访问性。
    • 支持通过点击标记来更新范围值,并引入了自定义句柄渲染的功能。
    • 改进了键盘导航,方向键可用于增减控制。
  • 文档
    • 更新了 README.md,包含 ariaRequired 属性的详细信息。
  • 测试
    • 添加了测试用例,以验证 aria-required 属性在句柄上的存在。

Copy link

vercel bot commented Nov 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
slider ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 24, 2024 11:00pm

Copy link

coderabbitai bot commented Nov 20, 2024

Walkthrough

此拉取请求引入了一个新的属性 ariaRequiredSlider 组件的 API 部分,以增强可访问性,允许开发者指定滑块手柄的 aria-required 属性。该属性在 Slider API 表中列出,类型为 string,默认值为 -。此外,还对 HandlePropsSliderProps 接口进行了相应更新,以支持此新属性。其他功能和文档结构保持不变,确保新属性与现有文档框架无缝集成。

Changes

文件路径 更改摘要
README.md 添加属性 ariaRequiredSlider API 部分,类型为 string,默认值为 -
src/Handles/Handle.tsx HandleProps 接口中添加 ariaRequired 属性,并将其应用于组件的内部逻辑。
src/Slider.tsx SliderProps 接口中添加 ariaRequired,并改进组件功能,包括点击标记更新范围值和自定义手柄渲染。
src/context.ts SliderContextProps 接口中添加可选属性 ariaRequired,类型为 `"true"
tests/Slider.test.js 添加测试用例以检查当 ariaRequired 属性设置为 'true' 时,滑块手柄是否具有 aria-required 属性。

Possibly related PRs

Poem

在滑块上,新增一属性,
ariaRequired,可访问性提升,
让用户输入更清晰,
兔子们欢呼,跳跃不停,
代码更新,功能更全,
一起享受这美好时光! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Nov 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.39%. Comparing base (97e960e) to head (e1a3a9d).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1051   +/-   ##
=======================================
  Coverage   99.39%   99.39%           
=======================================
  Files          14       14           
  Lines         661      661           
  Branches      191      199    +8     
=======================================
  Hits          657      657           
  Misses          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

README.md Outdated Show resolved Hide resolved
Co-authored-by: afc163 <[email protected]>
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (3)
src/context.ts (1)

18-18: 代码变更正确,建议添加属性文档注释

新增的 ariaRequired 属性类型定义正确,且与其他 ARIA 相关属性放置在一起,符合代码组织逻辑。建议添加 JSDoc 注释说明该属性的用途和使用场景。

建议添加如下注释:

+  /** 指定滑块是否为必填项,用于提升表单可访问性 */
   ariaRequired?: "true" | "false";
README.md (1)

135-135: 建议改进属性描述以保持一致性

为了与文档中其他 ARIA 相关属性保持一致,并提供更清晰的用途说明,建议修改描述。

-| ariaRequired | string | - | Set the `aria-required` attribute on the slider handle. |
+| ariaRequired | string | - | 设置滑块手柄的 `aria-required` 属性,用于指示此滑块是否为必填项。当设置为 "true" 时,辅助技术会通知用户该字段为必填项。 |
tests/Slider.test.js (1)

444-450: 测试实现正确但覆盖率可以提高

测试用例遵循了文件中其他 aria 属性测试的模式,实现正确。建议添加以下测试场景以提高覆盖率:

  it('sets aria-required on the handle', () => {
    const { container } = render(<Slider ariaRequired='true' />);
    expect(container.getElementsByClassName('rc-slider-handle')[0]).toHaveAttribute(
      'aria-required',
      'true',
    );
  });

+ it('does not set aria-required when prop is not provided', () => {
+   const { container } = render(<Slider />);
+   expect(container.getElementsByClassName('rc-slider-handle')[0]).not.toHaveAttribute('aria-required');
+ });
+
+ it('sets aria-required to false when explicitly set', () => {
+   const { container } = render(<Slider ariaRequired='false' />);
+   expect(container.getElementsByClassName('rc-slider-handle')[0]).toHaveAttribute(
+     'aria-required',
+     'false'
+   );
+ });
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 97e960e and e1a3a9d.

📒 Files selected for processing (5)
  • README.md (1 hunks)
  • src/Handles/Handle.tsx (2 hunks)
  • src/Slider.tsx (4 hunks)
  • src/context.ts (1 hunks)
  • tests/Slider.test.js (1 hunks)
🔇 Additional comments (5)
src/context.ts (1)

18-18: 验证相关组件中的实现

需要确保此属性在 Handle 组件中正确应用到 DOM 元素上。

运行以下脚本以验证实现:

✅ Verification successful

ariaRequired 属性已正确实现

通过代码分析可以确认:

  • Handle 组件(src/Handles/Handle.tsx)正确地将 ariaRequired 属性映射到了 aria-required DOM 属性
  • Slider 组件正确传递该属性到 Handle 组件
  • 已包含相关测试用例验证此功能
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 描述:检查 Handle 组件是否正确使用了 ariaRequired 属性

# 查找 Handle 组件中的 aria-required 属性使用
ast-grep --pattern 'aria-required={$_}'

# 查找相关测试用例
rg -l "aria-required.*test" 

Length of output: 71


Script:

#!/bin/bash
# 搜索包含 Handle 组件定义的文件
fd -e ts -e tsx Handle

# 搜索 Handle 组件的实现,查看属性的使用
ast-grep --pattern 'function Handle($$$) {
  $$$
}'

# 搜索 Handle 组件的属性定义
ast-grep --pattern 'interface HandleProps {
  $$$
}'

# 搜索任何包含 ariaRequired 的代码
rg "ariaRequired"

Length of output: 685

src/Handles/Handle.tsx (2)

64-64: 代码变更符合预期!

ariaRequired 属性的添加位置正确,与其他 ARIA 相关属性保持一致的代码风格。


172-172: 实现正确,建议验证文档完整性!

aria-required 属性的实现采用了 getIndex 辅助函数,与其他 ARIA 属性保持一致的处理方式。

建议验证以下几点:

  1. 确保新属性在组件文档中有清晰的使用说明
  2. 验证 TypeScript 类型定义的完整性

运行以下脚本来验证文档和类型定义:

✅ Verification successful

文档和类型定义已完整实现,无需额外修改

通过验证发现:

  • ariaRequired 属性已在 README.md 中有清晰的说明文档
  • TypeScript 类型定义在 context.tsSlider.tsx 中已正确声明为 "true" | "false"
  • 属性在组件层级间的传递链路完整:Slider -> Handle -> DOM 属性
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 检查文档和类型定义的完整性

# 查找文档中是否包含 ariaRequired 的说明
rg -i "ariaRequired" "README.md" "docs/"

# 检查相关的类型定义文件
fd -e ts -e tsx | xargs rg "ariaRequired"

Length of output: 502

src/Slider.tsx (2)

184-184: 属性解构中正确添加了 ariaRequired

在属性解构中新增了 ariaRequired,确保了该属性能够在组件中正确使用。


547-547: 在上下文中传递 ariaRequired 属性

已将 ariaRequired 属性添加到 SliderContext 中,确保其能够在子组件中被访问和使用,实现了属性的有效传递。

Also applies to: 566-566

@@ -112,6 +112,7 @@ export interface SliderProps<ValueType = number | number[]> {
tabIndex?: number | number[];
ariaLabelForHandle?: string | string[];
ariaLabelledByForHandle?: string | string[];
ariaRequired?: "true" | "false";
Copy link

@coderabbitai coderabbitai bot Nov 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

添加的 ariaRequired 属性类型定义有误

ariaRequired?: "true" | "false"; 中的类型限定为字符串 "true""false",但根据 WAI-ARIA 规范,aria-required 属性值应为布尔类型。建议将类型修改为 boolean,以避免类型不匹配的问题。

建议修改代码如下:

- ariaRequired?: "true" | "false";
+ ariaRequired?: boolean;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
ariaRequired?: "true" | "false";
ariaRequired?: boolean;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@afc163,感谢您的确认!


If you found this review helpful, would you consider giving us a shout-out on X?
Thank you for using CodeRabbit!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants