-
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
[RNMobile] Fix issue related to receiving undefined ref in text color format #56686
Merged
fluiddot
merged 5 commits into
trunk
from
rnmobile/fix/text-color-format-props-undefined
Dec 1, 2023
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
91e9e27
Fix issue related to receiving undefined ref in text color format
fluiddot ac58714
Update `react-native-editor` changelog
fluiddot a2b4784
Add test to cover undefined `contentRef` case
fluiddot c79cca2
Correct typo in `changelog`
fluiddot 72b276a
Merge branch 'trunk' into rnmobile/fix/text-color-format-props-undefined
fluiddot 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
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
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
Oops, something went wrong.
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.
This logic relies on the fact that the ref object (
contentRef
), passed from theRichText
component, contains the props passed to theAztecView
component.gutenberg/packages/format-library/src/text-color/index.native.js
Lines 51 to 58 in a2b4784
gutenberg/packages/format-library/src/text-color/index.native.js
Lines 65 to 86 in a2b4784
gutenberg/packages/block-editor/src/components/rich-text/native/format-edit.js
Line 40 in a2b4784
gutenberg/packages/block-editor/src/components/rich-text/native/index.native.js
Lines 1336 to 1337 in a2b4784
gutenberg/packages/block-editor/src/components/rich-text/native/index.native.js
Lines 1269 to 1272 in a2b4784
In theory, the props are not exposed in ref objects, so I investigated further where are they coming from. I couldn't pinpoint the code from React/React Native but I confirmed that ref objects coming from native components (like
Aztec
orVideo (react-native-video)
contain extra properties likeprops
orforceUpdate
. On the other hand, I couldn't find any documentation related to this, so I assume this approach is not recommended and might lead to issues in future React Native versions.