Conversation
The main change required is replacing `ios_update_metadata_source` (now deprecated) with `gp_update_metadata_source`
Generated by 🚫 Danger |
fastlane/lanes/localization.rb
Outdated
| # app_store_name: { | ||
| # path: File.join(source_metadata_folder, 'name.txt'), | ||
| # comment: "translators: The application name in the Apple App Store. Please keep the brand names ('Jetpack' and WordPress') verbatim. Limit to 30 characters including spaces and punctuation!" | ||
| # }, | ||
| # app_store_subtitle: { | ||
| # path: File.join(source_metadata_folder, 'subtitle.txt'), | ||
| # comment: 'translators: Subtitle to be displayed below the application name in the Apple App Store. Limit to 30 characters including spaces and commas!' | ||
| # }, | ||
| # app_store_desc: { | ||
| # path: File.join(source_metadata_folder, 'description.txt'), | ||
| # comment: 'translators: Multi-paragraph text used to display in the Apple App Store.' | ||
| # }, | ||
| # app_store_keywords: { | ||
| # path: File.join(source_metadata_folder, 'keywords.txt'), | ||
| # comment: <<~COMMENT.chomp | ||
| # translators: Keywords used in the App Store search engine to find the app. | ||
| # Delimit with a comma between each keyword. Limit to 100 characters including spaces and commas. | ||
| # COMMENT | ||
| # }, | ||
| # **(1..6).to_h do |i| | ||
| # [ | ||
| # "screenshot-text-#{i}", | ||
| # { path: File.join(custom_metadata_folder, "promo_screenshot_#{i}.txt"), comment: screenshot_comment } | ||
| # ] | ||
| # end |
There was a problem hiding this comment.
Given this entire part is (already was) commented out, now with the new idempotent PO generation, it removes the parts that are not present. Not sure if this is an issue to the tests the team is doing with the App Store copy? cc @crazytonyli
There was a problem hiding this comment.
According to git blame this was indeed commented out due to an ongoing ASO experiment… but that was ≈3 years ago! (Oct 2023)
Also even if we end up deciding to keep it commented out for the time being, we should still (1) update this code—so that it works out of the box when we might hopefully finally uncomment it in the future—and (2) DRY the common translator comments that are common for WP vs JP in some constants to avoid repetition.
There was a problem hiding this comment.
I have no idea what this ASO experiment is. Keeping or removing the comments both sounds good to me.
There was a problem hiding this comment.
we should still (1) update this code—so that it works out of the box when we might hopefully finally uncomment it in the future
Oh that's what the PR initially already did.
But now I've uncommented it (121ef3b) and re-generated WordPress/Jetpack/Resources/AppStoreStrings.po.
I'm tempted to keep it like that, so that the code is again in sync with the store, the code is running again, etc.
I've checked the fields such as app_store_name, app_store_desc, app_store_subtitle, etc and everything seems to match with ASC. The <version>-whats-new matches but it was already uncommented before.
The screenshots don't seem to be generated anymore though?
(2) DRY the common translator comments
I'd say The duplication is small and each lane reads well as a self-contained unit. Maybe we could consolidate into a single lane with different parameters (like a Jetpack / WordPress configuration stored in a hash 🤔 ), but at that point that'd be a larger refactoring that we could leave for later and that could apply to a lot of lanes.
AliSoftware
left a comment
There was a problem hiding this comment.
LGTM, but I think we should wait for Tony (or whoever might know in the WP/JP team) to answer about the JP metadata being currently disabled before merging, as I expect/hope the conclusion will end up being that we should uncomment it and resume JP metadata sync by now before merging…
fastlane/lanes/localization.rb
Outdated
| # app_store_name: { | ||
| # path: File.join(source_metadata_folder, 'name.txt'), | ||
| # comment: "translators: The application name in the Apple App Store. Please keep the brand names ('Jetpack' and WordPress') verbatim. Limit to 30 characters including spaces and punctuation!" | ||
| # }, | ||
| # app_store_subtitle: { | ||
| # path: File.join(source_metadata_folder, 'subtitle.txt'), | ||
| # comment: 'translators: Subtitle to be displayed below the application name in the Apple App Store. Limit to 30 characters including spaces and commas!' | ||
| # }, | ||
| # app_store_desc: { | ||
| # path: File.join(source_metadata_folder, 'description.txt'), | ||
| # comment: 'translators: Multi-paragraph text used to display in the Apple App Store.' | ||
| # }, | ||
| # app_store_keywords: { | ||
| # path: File.join(source_metadata_folder, 'keywords.txt'), | ||
| # comment: <<~COMMENT.chomp | ||
| # translators: Keywords used in the App Store search engine to find the app. | ||
| # Delimit with a comma between each keyword. Limit to 100 characters including spaces and commas. | ||
| # COMMENT | ||
| # }, | ||
| # **(1..6).to_h do |i| | ||
| # [ | ||
| # "screenshot-text-#{i}", | ||
| # { path: File.join(custom_metadata_folder, "promo_screenshot_#{i}.txt"), comment: screenshot_comment } | ||
| # ] | ||
| # end |
There was a problem hiding this comment.
According to git blame this was indeed commented out due to an ongoing ASO experiment… but that was ≈3 years ago! (Oct 2023)
Also even if we end up deciding to keep it commented out for the time being, we should still (1) update this code—so that it works out of the box when we might hopefully finally uncomment it in the future—and (2) DRY the common translator comments that are common for WP vs JP in some constants to avoid repetition.
|
| lane :update_wordpress_appstore_strings do |options| | ||
| lane :update_wordpress_appstore_strings do |version: release_version_current, skip_commit: false| | ||
| source_metadata_folder = File.join(PROJECT_ROOT_FOLDER, 'fastlane', 'metadata', 'default') | ||
| custom_metadata_folder = File.join(PROJECT_ROOT_FOLDER, 'fastlane', 'appstoreres', 'metadata', 'source') |
There was a problem hiding this comment.
🎗️ Worth taking note (Linear issue?) that it would be nice to get rid of the appstoreres at some point, to remove the confusion of having 2 different sources of truth for different App Store strings, like Gio recently did in another product (can't remember which)



Fixes AINFRA-1898, AINFRA-1899
Summary
ios_update_metadata_sourcewithgp_update_metadata_sourceTesting
bundle exec fastlane update_jetpack_appstore_strings skip_commit:true/bundle exec fastlane update_wordpress_appstore_strings skip_commit:trueto test PO generation