-
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 crash when editing a component that uses RangeControl #27987
[RNMobile] Fix crash when editing a component that uses RangeControl #27987
Conversation
Update `master` branch from original repo.
Update master branch from original repo
Update master branch from original repo.
Update master branch from original repo
Update master branch from original repo.
Update master branch from original repo
Update master branch from original repo
Update master branch from original repo
if ( onComplete ) { | ||
onComplete( nextValue ); | ||
} |
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.
My first attempt was to pass the handler in the Spacer block but then I realised that it would require to add it in more blocks so a better solution was to make it optional.
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.
Tested it on iOS and Android and everything works well. Thanks, @fluiddot for this PR!
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.
LGTM! Thanks for fixing it!
Re-ran failing test 🤞 |
Update master branch from original repo
Range cell component is used in multiple components but not all of them require the onComplete handler so it should be optional.
Range cell component is used in multiple components but not all of them require the onComplete handler so it should be optional.
* Release script: Update react-native-editor version to 1.44.0 * Release script: Update with changes from 'npm run core preios' * Mobile - Link settings - Fix data not being saved when closing the bottom sheet (#27997) * Set onComplete handler as optional in Range cell component (#27987) Range cell component is used in multiple components but not all of them require the onComplete handler so it should be optional. * Mobile - Link settings - Check for onClose (#28039) * Fix: Add Image style settings for hotlinked images (#28006) * Update CHANGELOG.md (#28042) * Change spaces back to tabs Co-authored-by: Gerardo Pacheco <[email protected]> Co-authored-by: Carlos Garcia <[email protected]> Co-authored-by: Enej Bajgoric <[email protected]>
* Release script: Update react-native-editor version to 1.44.0 * Release script: Update with changes from 'npm run core preios' * Mobile - Link settings - Fix data not being saved when closing the bottom sheet (#27997) * Set onComplete handler as optional in Range cell component (#27987) Range cell component is used in multiple components but not all of them require the onComplete handler so it should be optional. * Mobile - Link settings - Check for onClose (#28039) * Fix: Add Image style settings for hotlinked images (#28006) * Update CHANGELOG.md (#28042) * Change spaces back to tabs * Release script: Update react-native-editor version to 1.44.1 * Release script: Update with changes from 'npm run core preios' * [RNMobile] Fix crash in mobile paragraph blocks with custom font size (#28121) * Remove px suffix from fontSize for Android paragraph * Issue does not seem to be limited to android on latest gutenberg master * Move fontSize char removal to richtext to account for multiple block errors * Add move to top bottom when long pressing block movers (#27554) * WC: Added move to top and bottom functionality via long pressing BlockMover buttons and clicking the button on the BottomSheet Picker. * WIP: Unit tests. * WC: WIP unit tests for add move to top and bottom * WC: Moving UI tests to gutenberg with other UI tests instead of keeping at gutenberg-mobile. Adding more convenience functions to EditorPage. * WIP: Unit tests. * WC: Adding icon and title to picker for move to top/bottom. * WC: Cleaning up code. * WC: Fixing merge issue where import was changed to const. * WC: Changing all imports to requires as per jest bug. * WC: Removing before/afterAll blocks from UI tests. * WC: Removing e2e tests to issue-1191-add-move-to-top-bottom-ui-tests branch. * WC: Updating imports to fall in line with other files. Co-authored-by: Wendy Chen <[email protected]> * Fixed crash introduced from recent fontSize fix (#28209) * Updated changelog Co-authored-by: Paul Von Schrottky <[email protected]> Co-authored-by: Gerardo Pacheco <[email protected]> Co-authored-by: Carlos Garcia <[email protected]> Co-authored-by: Enej Bajgoric <[email protected]> Co-authored-by: illusaen <[email protected]> Co-authored-by: Wendy Chen <[email protected]>
Fixes #28081
Description
The crash was caused because
RangeCell
(the native component used inRangeControl
) was calling theonComplete
prop but not all the components that use it pass this handler. Since not all the components require this handler I changed it to be optional.Looks like the bug was introduced in the Full width columns PR, I checked that some components were updated but only the ones that use the
UnitControl
component which is the other one that usesRangeCell
underneath.How has this been tested?
This can also be tested with other components that have a slider and an input box for editing block's settings, like:
Screenshots
iPhone 8 simulator
edit-spacer-block-ios.mp4
Pixel 4 emulator
edit-spacer-block-android.mp4
Types of changes
Bug fix
Checklist: