refactor(components): [descriptions] use type-based definitions#23434
Conversation
📝 WalkthroughWalkthroughReplaces runtime prop objects with explicit TypeScript prop interfaces for Descriptions and DescriptionsRow, adds exported interfaces Changes
Sequence Diagram(s)(omitted) 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/descriptions/src/description.vue`:
- Around line 36-52: The change sets a default empty string for labelWidth in
the withDefaults call, which alters runtime behavior by turning previously
undefined labelWidth into ''—remove labelWidth from the defaults object so
defineProps<DescriptionProps>() retains undefined when not provided; update the
withDefaults/defaults block referencing props and DescriptionProps (and ensure
any consumers checking labelWidth === undefined still work).
|
🧪 Playground Preview: https://element-plus.run/?pr=23434 |
|
@SevenDreamYang Thanks for your contribution! ❤️ |

Please make sure these boxes are checked before submitting your PR, thank you!
devbranch.ref #23399
Other Notes
descriptionitemwas not refactored because ofdefineComponentSummary by CodeRabbit
Refactor
Deprecations
✏️ Tip: You can customize this high-level summary in your review settings.