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(picker): add picker-column selected class support #3216

Open
wants to merge 1 commit into
base: v4
Choose a base branch
from

Conversation

penjj
Copy link

@penjj penjj commented Oct 24, 2024

这个 PR 做了什么? (简要描述所做更改)
给 Picker 当前选中的行增加了一个 className, 已便于当前调整选中行的样式

这个 PR 是什么类型? (至少选择一个)

  • feat: 新特性提交
  • fix: bug 修复
  • docs: 文档改进
  • style: 组件样式/交互改进
  • type: 类型定义更新
  • perf: 性能、包体积优化
  • refactor: 代码重构、代码风格优化
  • test: 测试用例
  • chore(deps): 依赖升级
  • chore(demo): 演示代码改进
  • chore(locale): 国际化改进
  • chore: 其他改动(是关于什么的改动?)

这个 PR 涉及以下平台:

  • NutUI H5 @nutui/nutui
  • NutUI Taro @nutui/nutui-taro

这个 PR 是否已自测:

Summary by CodeRabbit

  • 新功能
    • 改进了选择器组件的视觉反馈,选中项有更明显的视觉指示。
    • 根据环境类型优化了确认逻辑,确保在不同环境下的选择确认准确无误。

Copy link

coderabbitai bot commented Oct 24, 2024

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

218 files out of 300 files are above the max files limit of 75. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

此次更改涉及src/packages/__VUE/picker/index.taro.vue文件的模板和脚本部分。模板中为表示选择项的视图元素添加了一个新的类名'nut-picker-roller-item-tarotile--selected',以便在索引与defaultIndexes值匹配时提供可视化反馈。脚本中更新了confirmHandler函数,添加了环境类型的条件检查,以确保在Web环境中选择确认时停止滚动。此外,tileChange函数也进行了修改,以更准确地处理选择项的变化。

Changes

文件路径 更改摘要
src/packages/__VUE/picker/index.taro.vue - 模板中添加类名'nut-picker-roller-item-tarotile--selected'以增强选择项的视觉反馈。
- 更新confirmHandler函数以根据环境类型调整确认逻辑。
- 修改tileChange函数以准确处理选择项的变化。

Possibly related PRs

Poem

在兔子窝里欢快跳,
选项变换如梦绕。
新的类名闪闪亮,
选择确认不再慌。
小小变化大不同,
兔子乐享新风光! 🐰✨


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

@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: 0

🧹 Outside diff range and nitpick comments (2)
src/packages/__VUE/picker/index.taro.vue (2)

Line range hint 123-137: 建议优化确认处理逻辑

当前实现在非 Web 环境下使用 setTimeout(confirm, 0) 可能不够可靠。建议考虑使用更稳定的方式处理确认事件。

建议如下改进:

 if (state.picking) {
-  setTimeout(() => {
-    confirm()
-  }, 0)
+  // 使用 nextTick 或 Promise 来确保在下一个事件循环执行
+  Promise.resolve().then(() => {
+    confirm()
+  })
 } else {
   confirm()
 }

Line range hint 150-160: 建议优化索引变化检测逻辑

当前的索引变化检测使用循环实现,可以使用数组方法优化代码可读性。

建议如下改进:

- let changeIndex = 0
- // 判断变化的是第几个
- for (let i = 0; i < data.detail.value?.length; i++) {
-   if (prevDefaultValue[i] !== data.detail.value?.[i]) {
-     changeIndex = i
-     break
-   }
- }
+ const changeIndex = data.detail.value?.findIndex(
+   (value: number, index: number) => prevDefaultValue[index] !== value
+ ) ?? -1
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 48a4887 and 6875843.

📒 Files selected for processing (1)
  • src/packages/__VUE/picker/index.taro.vue (1 hunks)
🔇 Additional comments (1)
src/packages/__VUE/picker/index.taro.vue (1)

40-41: 选中状态样式实现正确!

新增的类名绑定实现合理,同时保持了对原有 className 的支持。这种实现方式既保证了基础功能,又提供了良好的样式自定义能力。

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

Successfully merging this pull request may close these issues.

1 participant