[App size reduction] Optimize login-related, Blaze, and empty store assets #15881
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.
Part of WOOMOB-534
Description
In this PR we switch several assets for their optimized versions, so we can reduce the data binaries
Looping in Kiwi as are mostly related to login, blaze, and store selection, with a side quest for taxes:
Testing information
Case 3: Woo store selection
I couldn't find the actual case where this is trigger. It should happen during the authentication process, when you're already logged into a WooCommerce store, but you have no WooCommerce stores (?) . It would seem is legacy code from a previous authentication flow but this is no longer possible, so if that's the case we could remove the whole thing rather than just updating the assets, which can be done on a separate PR. In any case, I've confirmed that the assets look the same in /Assets, just couldn't trigger the actual case in-app.
Case 4: Tax rates
Set New tax rate
. If no tax rates are set up in wp-admin you'll see this screen. If some are already set up please remove them or switch the case just for testing inNewTaxRateSelectorView.viewModel.syncState.empty
RELEASE-NOTES.txt
if necessary.