You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add code to ensure locales declaration consistency
By comparing the locales limited by the `resourcesConfiguration` field in a product flavor with the ones we hardcoded in our Fastlane scripts.
This way if we decide to update either place in the future (e.g. add new locales to download from GlotPress for Jetpack by updating the `JP_APP_LOCALES` constant in `fastlane/lanes/localization.rb`) we'll be reminded to ensure we updated the other as well (i.e. the `resourceConfigurations` in the `jetpack` flavor of the `WordPress/build.gradle` file)
UI.message("The `resourceConfigurations` field set in `build.gradle` for the `#{app_flavor}` flavor matches what is set in our Fastfile. All is good!")
442
+
else
443
+
UI.user_error!<<~ERROR
444
+
The list of `resourceConfigurations` declared in your `build.gradle` for the `#{app_flavor}` flavor
445
+
does not match the list of locales we hardcoded in the `fastlane/lanes/localization.rb` for this app.
446
+
447
+
If you recently updated the hardcoded list of locales to include for this app, be sure to apply those
448
+
changes in both places, to keep the Fastlane scripts consistent with the gradle configuration of your app.
0 commit comments