Skip to content

Conversation

wzc520pyfm
Copy link

@wzc520pyfm wzc520pyfm commented Jun 23, 2025

在特殊业务场景下,我需要为RangPicker的起始时间和结束时间采用不同的格式化:
image
现有的api似乎无法做到,结合目前的format prop设计,只要将range的索引传递给customFormat即可实现:

Preview:

image

Summary by CodeRabbit

  • 新功能
    • 在范围选择器示例中新增“自定义格式”用法,支持分别自定义起止日期的显示格式(如仅显示年份或完整日期)。
  • 文档
    • 增加了“自定义格式”相关的使用示例,便于理解格式化函数的用法。
  • 类型优化
    • 自定义格式化函数现支持接收索引参数,便于区分和处理不同位置的日期格式。
@vercel
Copy link

vercel bot commented Jun 23, 2025

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

Name Status Preview Comments Updated (UTC)
picker ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 25, 2025 1:42pm
@coderabbitai
Copy link

coderabbitai bot commented Jun 23, 2025

Walkthrough

本次更改为 RangePicker 组件引入了自定义格式化示例,并将自定义格式化函数的签名扩展为支持索引参数。相关类型定义、工具函数和钩子均已同步调整,以便格式化函数能够接收并利用日期项的索引信息。

Changes

文件/分组 变更简述
docs/examples/range.tsx 新增“Custom Format”示例,展示带索引的自定义格式化 RangePicker。
src/interface.tsx CustomFormat 类型签名增加 index 参数。
src/utils/dateUtil.ts formatValue 函数增加 index 参数,调用格式化函数时传递索引。
src/PickerInput/Selector/hooks/useInputProps.ts getText 回调函数签名增加 index 参数,相关调用同步调整。

Sequence Diagram(s)

sequenceDiagram participant User participant RangePicker participant formatValue participant CustomFormat User->>RangePicker: 选择日期范围 RangePicker->>formatValue: formatValue(date, { format, index }) formatValue->>CustomFormat: CustomFormat(date, index) CustomFormat-->>formatValue: 返回格式化字符串 formatValue-->>RangePicker: 返回格式化结果 RangePicker-->>User: 显示格式化后的日期文本 
Loading

Suggested reviewers

  • zombieJ

Poem

🐇
代码如春草,格式随心调,
索引添新意,日期更美妙。
RangePicker 展示,示例闪光耀,
格式自定义,灵活真高超!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/PickerInput/Selector/hooks/useInputProps.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

Error: Cannot read config file: /.eslintrc.js
Error: Cannot find module '@umijs/fabric/dist/eslint'
Require stack:

  • /.eslintrc.js
  • /node_modules/.pnpm/@eslint+eslintrc@2.1.4/node_modules/@eslint/eslintrc/dist/eslintrc.cjs
  • /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli-engine/cli-engine.js
  • /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/eslint.js
  • /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/index.js
  • /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli.js
  • /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/bin/eslint.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1405:15)
    at require.resolve (node:internal/modules/helpers:145:19)
    at Object. (/.eslintrc.js:2:21)
    at Module._compile (node:internal/modules/cjs/loader:1734:14)
    at Object..js (node:internal/modules/cjs/loader:1899:10)
    at Module.load (node:internal/modules/cjs/loader:1469:32)
    at Module._load (node:internal/modules/cjs/loader:1286:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.require (node:internal/modules/cjs/loader:1491:12)

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between abd1bba and 8209369.

📒 Files selected for processing (1)
  • src/PickerInput/Selector/hooks/useInputProps.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/PickerInput/Selector/hooks/useInputProps.ts
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this 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

🧹 Nitpick comments (1)
docs/examples/range.tsx (1)

205-215: 很好的功能演示示例

这个示例清晰地展示了如何使用索引参数对范围选择器的开始和结束日期应用不同的格式。实现简洁明了,很好地说明了新功能的用法。

不过建议考虑格式化逻辑的一致性:对于年份选择器,两个日期都使用 YYYY 格式可能更合理。

 format={(date, index) => { - return index === 0 ? date.format('YYYY') : date.format('YYYY-MM-DD'); + return index === 0 ? date.format('YYYY') : date.format('YYYY'); }}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d3dc263 and abd1bba.

📒 Files selected for processing (4)
  • docs/examples/range.tsx (1 hunks)
  • src/PickerInput/Selector/hooks/useInputProps.ts (2 hunks)
  • src/interface.tsx (1 hunks)
  • src/utils/dateUtil.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
src/PickerInput/Selector/hooks/useInputProps.ts (1)
src/utils/dateUtil.ts (1)
  • formatValue (229-250)
src/utils/dateUtil.ts (2)
src/generate/index.ts (1)
  • GenerateConfig (1-46)
src/interface.tsx (2)
  • Locale (6-84)
  • CustomFormat (284-284)
🔇 Additional comments (5)
src/interface.tsx (1)

284-284: 类型签名更新合理,支持按范围索引格式化

CustomFormat 类型新增的 index 参数能够让格式化函数区分日期在范围中的位置,这为实现不同的开始和结束日期格式提供了基础。类型定义清晰明确。

src/PickerInput/Selector/hooks/useInputProps.ts (2)

89-90: 正确实现索引参数传递

getText 回调函数的签名更新合理,能够将索引参数正确传递给 formatValue 函数,确保格式化函数能够获取到位置信息。


101-101: 合理的默认索引值

firstFormat 函数调用传递索引 0 是合理的,因为这里是在计算输入框大小时使用第一个格式。这保持了与现有逻辑的一致性。

src/utils/dateUtil.ts (2)

235-241: 良好的向后兼容性设计

index 参数提供默认值 0 确保了向后兼容性,同时类型定义也正确地将其标记为可选参数。这种设计允许现有代码无缝继续工作。


247-249: 正确的条件格式化实现

format 为函数时正确传递 index 参数,当为字符串时使用原有的格式化逻辑。这种实现方式确保了功能的正确性和兼容性。

@codecov
Copy link

codecov bot commented Jun 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.80%. Comparing base (d3dc263) to head (8209369).

Additional details and impacted files
@@ Coverage Diff @@ ## master #932 +/- ## ======================================= Coverage 98.80% 98.80% ======================================= Files 65 65 Lines 2669 2670 +1 Branches 742 716 -26 ======================================= + Hits 2637 2638 +1  Misses 29 29 Partials 3 3 

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@afc163 afc163 requested a review from zombieJ July 22, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants