Mobile Release v1.79.0 #42239
Merged
Mobile Release v1.79.0 #42239
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
…nt to BlockListItemCell (#41105) * Mobile - BlockList - Pass FlatList internal onLayout through CellRendererComponent * Mobile - Update onLayout naming for BlockListItemCell
…41053) * Mobile - Fix - Drag & drop chip issue with RTL languages * Mobile - BlockDraggable - Rename maxWidth variable to contentWidth * Mobile - BlockDraggable - Add custom exiting animation that uses the same functionality as ZoomOutEasyDown but customizing the translateX value taking into account RTL languages.
* Add drag & drop help guide * Update content of help screen related to moving blocks * Update drand-and-drop images * Update styles of heading component of help screen * Add HelpDetailBadge component This component will be rendered in `HelpDetailSectionHeadingText` component via the `badge` prop. * Add NEW badge to move blocks help section * Optimize drag-and-drop images * Add move-blocks icon to Help & Support screen * Update react-native-editor changelog * Add HelpSectionTitle component * Prevent rendering separator on last help topic item
…ortcode block (#41155) * Add prop for disabling suggestions button * Use allowed formats in format types calculation * Add RichText version to PlainText component * Use experimental version of PlainText in Shortcode block * Add disableAutocorrection prop to RichText * Disable autocorrection in Shortcode block * Update PlainText props in Shortcode block * Use pre as tagName in PlainText * Rename replaceLineBreaks function * Update shortcode block unit tests * Prevent text input focus when selecting Shortcode block * Force text color in Shortcode block * Remove tagName prop from PlainText component
…ontrol (#41036) Improves the text that's read by screen readers by the BottomSheetSelectControl component, adding extra context and making its purpose clearer.
* Add 'Insert from URL' option to Video and Image blocks * Update code style from linting * Improve test cases for Media Upload capture options * Fix whitespace issue * Update Media Upload option tests to be asynchronous * Update native image block to use correct image URL * Add error handling for invalid URLs to native Image block * Clear invalid URL error on Image URL success * Fix synchronicity of Media Upload option tests * Add check for URL handler to native Image block picker options * Update code style * Remove Video block from urlSource options Why: to be introduced in a later PR * Remove URL option from Video block for Media Upload test * Use Notice snackbar for native Image block error handling * Update Image/Media Upload code style and helpers * Use getImage to determine if URL is a valid image within Image block * Add loading indicator and isURL check to native Image block URL behavior * Add loading indicator to native Image block media placeholder * Fix whitespace issue in native Image block code style * Reuse native Image block loading indicator * Use undefined dimension attributes for the native Image block URL behavior Co-authored-by: Derek Blank <[email protected]>
* update tests using paragraph, heading and list blocks * fix slash inserter tests to work in ci * lint fixes * wait for ordered list to appear * lint fixes * extra click only on local env * wait to get backspace click reflected * re-add extra click only for local env * add wait to wait for backspace key to be reflected * lint fixes * break function, set position to get list block * lint fixes * use correct params, update function name * lint fixes * make maxIteration a parameter for isElementVisible * update xpath for list block * utilize waitForVisible for isElementVisible * lint fixes * add wait to getNumberOfParagraphBlocks and update xpath for android list block * update edit text xpath to be read from any level Co-authored-by: jos <[email protected]>
Use same version of ruby that is used on WP iOS
* Update with copy from Gutenberg Mobile Gutenberg Mobile's readme had some copy in the troubleshooting section that wasn't included in Gutenberg's how-to: https://github.com/wordpress-mobile/gutenberg-mobile/edit/trunk/README.md This commit fixes that issue by updating Gutenberg's how-to with the latest from Gutenberg Mobile. * Tweak wording, update inconsistent capitalisation * Tweaks to copy and formatting With this commit, I've tidied up some of the copy, attempting to make the instructions as concise and helpful as possible. I've also set the images to the same width to tidy up the overall look of the document (the images will appear small on mobile devices, but can be tapped on to get the full image). * Set all images to fixed width, for consistency * Rearrange sections to improve overall flow - The "Unit Tests" is moved towards the bottom of the document, so that's it's closer to the instructions for integration tests. the document flows as follows: - The steps for installing Xcode are moved under the "iOS" section. - The overall flow of the document has been updated to the following: Clone Gutenberg > iOS > Android > Tests * Add details about recommended JDK * Add details about Cocoapods * Refine instructions for installing Cocoapods * Note `ffi` may already be installed Some versions of Ruby may not require the `ffi` to be manually installed, which is noted with this commit.
Co-authored-by: jos <[email protected]>
* add waits to all block - 1st try * fix failing tests * correct if else condition * fix failing cover block test * update spaces * update to use new click helper * wait for blocks to be visible first in getFirstBlock and getLastBlock * remove length as a parameter * update timing for long press since it's failing intermittently in ci * remove deleted param, revert space changes * remove redundant code * exit function once condition is met * increse wait time for long press * remove unneccesary condition, update message, return click value Co-authored-by: jos <[email protected]>
This reverts commit a046a61.
dcalhoun
added
the
Mobile App - i.e. Android or iOS
4 tasks
…41364) * Add testID prop to Draggable components * Add unit tests for Draggable component * Set draggingId shared value before enable dragging This change is required for testing, otherwise the dragging id is not passed when the dragging gesture begins. * Mock generateHapticFeedback function * Add testID to draggable chip component * Add testID to BlockDraggable component * Add test helpers for BlockDraggable component Additionally, helpers related to fake timers have been added and updated in the global helpers file. * Add drag and drop integration tests * Update react-native-aztec mock to use AztecInputState
* Mobile - Add E2E tests for the Drag & Drop blocks feature * Update longPress action * Use clickIfClickable * Use longPress instead of press * Fix clipboard typo * Add setClipboard and clearClipboard helpers
* Mobile - Skip some of the Drag & Drop E2E on iOS * Replace if condition to use onlyOnAndroid wrapper instead
…ForVisible() to control return value (#41367) Co-authored-by: jos <[email protected]>
* Add onSelectURL function to mobile Video block edit * Add notices store to mobile Video block * Display Insert from URL in Video block media options menu * Allow native video block to use Embed block for embeddable URLs * Update native Video block src onSelectURL attribute * Update CHANGELOG
* fix: Image block preserves alt text from media library When the alt text for a media item is present in the media library, that value should be copied into the Image block when inserted. This behavior avoids the need to re-enter the alt text for each image inserted into the post content. * fix: Allow Media with and without alt text Previous code required an alt text value, which broken existing code. This overrides the method to support both contexts. It also updates existing code to use the same method of generating media throughout the source. * test: Update alt text for demo editor test data Consistently setting the alt text for all platforms will likely help avoid confusion. * test: Update outdated test fixture data The demo editor now returns an alt text for the test image media. * docs: Update changelog
If a block's validation fails within the mobile app, users are shown an error but not provided with any options for recovering the block. This PR introduces an option for users to attempt block recovery. They'll be prompted to tap on a block if they wish to attempt recovery.
…42136) * Update Gradle to 7.4.1 * Update AGP to 7.2.1
dcalhoun
requested review from
ellatrix,
fluiddot,
geriux,
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
fluiddot
reviewed
Jul 8, 2022
| @@ -764,7 +764,7 @@ | |||
| "CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer"; | |||
| COPY_PHASE_STRIP = NO; | |||
| ENABLE_STRICT_OBJC_MSGSEND = YES; | |||
| "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = ""; | |||
There was a problem hiding this comment.
This change is usually caused by installing Pods using an x86 machine.
|
Size Change: 0 B Total Size: 1.25 MB ℹ️ View Unchanged
|
fluiddot
reviewed
Jul 11, 2022
Comment on lines
+521
to
+526
| react-native-keyboard-aware-scroll-view: 374b637c8684d7de50bd930df1a2d2b8fd49daa5 | ||
| react-native-safe-area: c9cf765aa2dd96159476a99633e7d462ce5bb94f | ||
| react-native-safe-area-context: f0906bf8bc9835ac9a9d3f97e8bde2a997d8da79 | ||
| react-native-safe-area-context: e471852c5ed67eea4b10c5d9d43c1cebae3b231d | ||
| react-native-slider: d4c3367c5db5d2bec3ac0ab9d15ebb73d896034c | ||
| react-native-video: 0b09cc469df0249509def5dc1484e0419342de9b | ||
| react-native-webview: 193d233c29eacce1f42ca2637dab7ba79c25a6de | ||
| react-native-video: 2ad952d1a9ce83e058dcb4a1800af3a99cb7edee | ||
| react-native-webview: 1f56115845c98f0a59dfbbac685797c014a821be |
There was a problem hiding this comment.
I'm wondering why the checksums have changed for these libraries if only we updated the version of Gutenberg and RNTAztecView 🤔. I've checked the Podfile.lock file changes in the previous release (reference) and looks like only Gutenberg and RNTAztecView changed.
There was a problem hiding this comment.
I've updated my PR and it brings back these references so I can restore them once I merge it, what do you think?
There was a problem hiding this comment.
I've updated my PR and it brings back these references so I can restore them once I merge it, what do you think?
Yeah, sounds good, let's bring them back on that PR as it will be merged soon.
There was a problem hiding this comment.
My understanding is that these types of changes are related to #32772 (comment), and are merely a result of pod install on different development machines with different paths. It might be a good practice to avoid committing this type of change to avoid confusion, however I do not know if one value is "correct."
There was a problem hiding this comment.
My understanding is that these types of changes are related to #32772 (comment), and are merely a result of pod install on different development machines with different paths.
Great, thanks for sharing the context. I'm wondering what's the difference between our machines 🤔. I see Ceyhun outlined in that comment a potential workaround, so it might be interesting to tackle that in the future.
It might be a good practice to avoid committing this type of change to avoid confusion, however I do not know if one value is "correct."
Yep, it's not clear which values are the "correct" ones. I guess something that could be used as a guide in release PRs is that only Gutenberg and RNTAztecView Pods should be updated, wdyt?
There was a problem hiding this comment.
Yep, it's not clear which values are the "correct" ones. I guess something that could be used as a guide in release PRs is that only
GutenbergandRNTAztecViewPods should be updated, wdyt?
Yes, that would likely be helpful guidance. Unnecessary Podfile.lock changes could still sneak in within non-release PRs, but guidance for releases is likely still beneficial.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Release 1.79.0 of the react-native-editor and Gutenberg-Mobile.
For more information about this release and testing instructions, please see the related Gutenberg-Mobile PR: wordpress-mobile/gutenberg-mobile#5011
Review
Since the PR includes a lot of file changes due to branching off from the previous release branch, we could check the exact charges that will be introduced by comparing the previous release tag (i.e. 1.78.1) with this branch:
rnmobile/1.78.1...rnmobile/release_1.79.0