refactor(components): [steps] use type-based definitions#23433
Conversation
📝 WalkthroughWalkthroughReplaces runtime ExtractPropTypes-based exported prop aliases with explicit TypeScript interfaces ( Changes
Sequence Diagram(s)(omitted — changes are type/public-API and do not introduce new multi-component runtime control flow) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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/steps/src/item.ts`:
- Around line 6-25: StepProps currently declares description and status as
required but they are given runtime defaults via withDefaults(); update the
interface so both description and status are optional (e.g., description?:
string and status?: '' | 'wait' | 'process' | 'finish' | 'error' | 'success') to
match Vue 3 conventions and the withDefaults() usage; locate the StepProps
interface in item.ts and change the two property signatures accordingly.
|
🧪 Playground Preview: https://element-plus.run/?pr=23433 |
|
@SevenDreamYang Thanks for your contribution! ❤️ |

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