-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
components: Promote Text to full components export #31291
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sarayourfriend
added
[Type] Breaking Change
For PRs that introduce a change that will break existing functionality
[Package] Components
/packages/components
[Feature] Component System
WordPress component system
labels
Apr 28, 2021
sarayourfriend
requested review from
ajitbohra and
chrisvanpatten
as code owners
April 28, 2021 15:38
Size Change: -388 B (0%) Total Size: 1.31 MB
ℹ️ View Unchanged
|
sarayourfriend
force-pushed
the
add/upgrade-text
branch
2 times, most recently
from
April 28, 2021 20:03
47990c0
to
820abc3
Compare
sarayourfriend
force-pushed
the
add/upgrade-text
branch
from
April 29, 2021 14:44
820abc3
to
195be4a
Compare
gziolo
force-pushed
the
add/upgrade-text
branch
from
April 30, 2021 09:07
195be4a
to
d1f1fe1
Compare
gziolo
force-pushed
the
add/upgrade-text
branch
from
April 30, 2021 09:36
d1f1fe1
to
3d9ae4e
Compare
gziolo
approved these changes
Apr 30, 2021
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.
I applied some additional changes:
- aligned the way we import components
- marked components as experimental in the documentation
- updates examples to use
__experimental
prefix
See 3d9ae4e.
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feature] Component System
WordPress component system
[Package] Components
/packages/components
[Type] Breaking Change
For PRs that introduce a change that will break existing functionality
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Replaces
Text
withui/Text
.This keeps the existing implementation for React native. I didn't actually see it being used in React native (React native has its own
Text
component) so I'm not sure we even need a React native implementation of this? Who would be best to ask?How has this been tested?
Run Gutenberg and test some controls as well as the spacer tooltip to ensure that they work as expected.
Types of changes
New feature.
Breaking change, but it's behind
__experimental
so I think it should be okay to make this breaking change.Checklist:
*.native.js
files for terms that need renaming or removal).