refactor(components): [row] use type-based definitions#23437
Conversation
📝 WalkthroughWalkthroughRow component props were converted from a runtime prop object to an explicit exported TypeScript Changes
Sequence Diagram(s)(omitted — changes are type-refactor and defaulting updates with no new multi-component control flow) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
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. Comment |
commit: |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@packages/components/row/src/row.ts`:
- Around line 36-38: The deprecation JSDoc on rowProps is misleading because
RowProps is a TypeScript type and doesn’t replace runtime validators/defaults;
update the comment on rowProps in row.ts to either remove the “Use `RowProps`
instead” suggestion or clarify that RowProps is type-only and does not supply
runtime validation/defaults, e.g., state that runtime consumers should continue
to use rowProps for validators/defaults while RowProps is the compile-time type,
and ensure the symbols mentioned are `rowProps` (runtime) and `RowProps` (type).
|
🧪 Playground Preview: https://element-plus.run/?pr=23437 |
|
@lw56777 Thanks for your contribution! ❤️ |

Please make sure these boxes are checked before submitting your PR, thank you!
devbranch.修复:#23399
Summary by CodeRabbit
New Features
Refactor
Deprecated
✏️ Tip: You can customize this high-level summary in your review settings.