-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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(components): add el-text component #11653
Conversation
👋 @gimjin, seems like this is your first time contribution to element-plus.
|
Create el-text idea by How to use Element-Plus only, forget inefficiency DIV+CSS? |
@gimjin thank you for the contribution, I will go through your PR and see if this matches our current design principle, we WILL ACCEPT this one eventually. |
@gimjin I was wondering if you can reorganize your commits into smaller pieces with
Dividing your changes into smaller ones will boost the review process. |
🧪 Playground Preview: https://element-plus.run/?pr=11653 |
To make this work, you will need to introduce this component in |
thanks for your guidance @jw-foss , I've adjusted as required.
|
Already modified code and pushed. @ryuhangyeong |
Do I want to synchronize with upstream/dev every push? I have just rebased the latest code. git rebase -i upstream/dev
git push -f |
Technically you don't. Your commits will be squashed and merged onto the HEAD, meaning that you will only have 1 commit in the end, as long as there were no conflicts I don't think you should rebase for every push. BTW, in practical Git, we don't really use |
#11724 PR is before this PR merged dev branch, github robot tip me behind and show MERGE BUTTON, after click the button robot auto create new I already know, only conflict when merging will rebase it. @jw-foss thanks gift |
e109446
to
9d8c0c5
Compare
@gimjin nice~ |
😸🥂 |
@gimjin thank you for your hard working!! I will review the ASAP 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gimjin good job and excellent work! I have no further comments but one for the API naming, would you mind address it so we can merge this one and get it released!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gimjin good job and excellent work! I have no further comments but one for the API naming, would you mind address it so we can merge this one and get it released!
I will merge this later this week, due to the hotfix tonight. |
@gimjin thank you for your excellent work and patient ❤️, I just merged this PR! Good job! 🚀 |
@gimjin Thank you for your hard work~ |
Thank you for review my graffiti code @jw-foss @ryuhangyeong @tolking @btea 🍻. I have developed ellipsis tooltip and line-clamp in my line-clamp branch, but unit test some exceptions in el-tooltip, I will create PR after fix. |
* test(components): [text] el-text unit test * docs(components): [text] el-text website documentation * feat(components): [text] el-text implementation * fix(components): [text] prop 'as' rename 'tag' * docs(components): [text] rename slot default, optimize document * test(components): [text] render text & class change the execution order * fix(components): [text] use template and render function together
Please make sure these boxes are checked before submitting your PR, thank you!
dev
branch.Because vitepress import from published element-plus, so el-text doc example not working. The docs only be packaged after published element-plus has el-text.
Locally review, build first, and edit example vue files: