Onboarding: Remove Pre-Launch checklist UI

[joemcgill]

Part of #2458

The 3rd step of the onboarding process includes this pre-launch check list at the bottom of the screen.

This checklist doesn't really add value to the user experience and can lead to someone either abandoning the onboarding process or just checking everything in order to move on. Let's remove this section to streamline the onboarding experience.

Acceptance Criteria

• On the 3rd step of onboarding, "Confirm store requirements", the pre-launch section is no longer shown
• The PreLaunchChecklist component is removed from the codebase (js/src/setup-mc/setup-stepper/store-requirements/pre-launch-checklist/index.js)
• Options related to the pre launch checklist should no longer be updated during this onboarding step once the PreLaunchChecklist is removed.

Implementation Brief

The PreLaunchChecklist component is defined in js/src/setup-mc/setup-stepper/store-requirements/pre-launch-checklist/index.js and imported into the StoreRequirements page in js/src/setup-mc/setup-stepper/store-requirements/index.js. We can likely just remove the PreLaunchChecklist component from the the StoreRequirements page and delete the file where it's defined, since it doesn't seem to be used anywhere else. This useEffect() hook (link) that updates the saved settings based on policyCheckData can also be removed.

Test Coverage

• Update E2E tests in tests/e2e/specs/setup-mc/step-3-confirm-store-requirements.test.js to remove tests related to the Pre-Launch Checklist.

Definition Questions

1. It looks like these checkboxes do actually trigger an HTTP request to the /wp-json/wc/gla/mc/settings endpoint, which ends up updating the DB option stored in gla_merchant_center but these values don't persist when the page is reloaded. Is there any other JS code that needs to be cleaned up when this is removed so the onboarding process doesn't affect the stored DB values if previously set?
2. The JEST tests for the pre-launch-checker would be removed. Are there other JEST tests or storybook snapshots that we need to plan to update?

[eason9487]

1. It looks like these checkboxes do actually trigger an HTTP request to the /wp-json/wc/gla/mc/settings endpoint, which ends up updating the DB option stored in gla_merchant_center but these values don't persist when the page is reloaded. Is there any other JS code that needs to be cleaned up when this is removed so the onboarding process doesn't affect the stored DB values if previously set?

Perhaps the JS codes related to the usePolicyCheck hook could be removed as well. For example, this code will no longer override the gla_merchant_center WP option.

google-listings-and-ads/js/src/setup-mc/setup-stepper/store-requirements/index.js

Lines 82 to 121 in a8e9cac

	// Preprocess the auto-checked state and data saving.
	useEffect( () => {
	if ( preprocessed || ! settings || ! policyCheckData ) {
	return;
	}
	const newSettings = { ...settings };
	const websiteLive =
	policyCheckData.allowed_countries &&
	! policyCheckData.robots_restriction &&
	! policyCheckData.page_not_found_error &&
	! policyCheckData.page_redirects;
	if ( websiteLive !== settings.website_live ) {
	newSettings.website_live = websiteLive;
	}
	if ( policyCheckData.store_ssl !== settings.checkout_process_secure ) {
	newSettings.checkout_process_secure = policyCheckData.store_ssl;
	}
	if ( policyCheckData.refund_returns !== settings.refund_tos_visible ) {
	newSettings.refund_tos_visible = policyCheckData.refund_returns;
	}
	if (
	policyCheckData.payment_gateways !==
	newSettings.payment_methods_visible
	) {
	newSettings.payment_methods_visible =
	policyCheckData.payment_gateways;
	}
	const promise = isEqual( newSettings, settings )
	? Promise.resolve()
	: saveSettings( newSettings );
	promise.finally( () => setPreprocessed( true ) );
	}, [ preprocessed, policyCheckData, settings, saveSettings ] );

2. The JEST tests for the pre-launch-checker would be removed. Are there other JEST tests or storybook snapshots that we need to plan to update?

I think there are no other jest tests that need to be update, and this should be clear when running jest tests after removal..

[joemcgill]

Perhaps the JS codes related to the usePolicyCheck hook could be removed as well. For example, this code will no longer override the gla_merchant_center WP option.

Thanks @eason9487, makes sense to me.

[mikkamp]

Closing this as completed since it was part of the 2.9 release.