-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add list props to rich text in native. #18748
Merged
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
761e503
Add list props to rich text in native.
SergioEstevao 0fb5bfd
Merge branch 'refs/heads/master' into rnmobile/list-settings
SergioEstevao c26f4e7
Merge branch 'refs/heads/master' into rnmobile/list-settings
SergioEstevao 3d176da
Merge branch 'refs/heads/master' into rnmobile/list-settings
SergioEstevao 23e4728
Make sure we remove root tags with extra attributes too
SergioEstevao 2fc6d6d
Adapt the keyboard of the control depending of the type of the control.
SergioEstevao bff7d16
Make sure component refresh when props start/reversed change.
SergioEstevao 0c4877e
Merge branch 'refs/heads/master' into rnmobile/list-settings
SergioEstevao File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
3 changes: 0 additions & 3 deletions
3
packages/block-library/src/list/ordered-list-settings.native.js
This file was deleted.
Oops, something went wrong.
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
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.
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.
Both these props are already added further down to
Editable
.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.
Would it be possible to make that work for native? Ideally all not rich text related props are directly passed to the editable element.
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.
So we don't have editable on native, and all of the props need to go trough rich text.
One thing that I was thinking was to create an TagAttributes property that will go along with TagName prop and controlled by the blocks.
What do you think @ellatrix ?
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.
Would it be possible to create an
Editable
on native?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.
It will be possible, but it will take some considerable work to get there, and out of scope for this PR.
We basically will need to make our Native Aztec rich text component to be the Editable and respect all the API for it.
@koke and @hypest may have more thoughts about this, and when to give it to priority.
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 talked with @ellatrix and we agree to keep this as it is, and tackle it on a separate PR.