-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare Analytics setup form UI for split into four sub-variants (depending GA4 support and available properties) #3247
Comments
IB ✔️ |
I will also update the estimate down to 7 since it seems like 11 is more than we need here. |
QA Update: Confirm with Engineer
|
@wpdarren I need to fix one issue with setup flow mode detection that causes this problem. I'll work on it. |
@felixarntz do you mind reviewing my PR #3352? It fixes issues with the Analytics setup form caused by incorrect work of the |
@felixarntz I created a new PR: #3386. Could you please take a look at it? |
QA ✅All good on my end. Tested UA properties and confirmed "SetupFormUA" was displayed. Tried to submit, confirmed nothing occurred. Sending to testing approval. |
As specified in #3170, the Analytics setup flow with GA4 support will be tiered into three different versions, one of which will be rendered based on the currently selected account and whether it has only UA properties, only GA4 properties, or properties of both types.
Then, in addition there is the existing UI which also needs to be maintained until we launch GA4 support (currently behind
ga4setup
feature flag). The existing UI is basically the UI for no GA4 support (which technically also means it only shows UA properties, but other than the new UI for that scenario the existing one doesn't even consider GA4 such as create matching properties).This issue is about splitting the Analytics
SetupForm
component to prepare for the 4 different variants.Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
assets/js/modules/analytics/components/setup
:SetupFormLegacy
SetupFormUA
SetupFormGA4
SetupFormGA4Transitional
SetupForm
component, specifically everything within theform
element except for the.googlesitekit-setup-module__action
with the submit button.SetupForm
should be moved as is intoSetupFormLegacy
. In other words, that component can already be completed here..googlesitekit-setup-module__inputs
container, for now with theAccountSelect
dropdown only..googlesitekit-setup-module__inputs
container, each of them should for now have a simple placeholderdiv
with text what they are for (e.g.SetupFormUA
should return<div>SetupFormUA</div>
).SetupForm
component should then be updated to conditionally render one of the four new components, based on thegetSetupFlowMode
selector:legacy
-->SetupFormLegacy
ua
-->SetupFormUA
ga4
-->SetupFormGA4
ga4transitional
-->SetupFormGA4Transitional
SetupMain
component: If thegetSetupFlowMode
selector returnsundefined
(i.e. not loaded), theProgressBar
condition should apply, i.e. the whole setup should show a loading state.legacy
case) remains intact.Implementation Brief
SetupFormLegacy
SetupFormUA
SetupFormGA4
SetupFormGA4Transitional
SetupForm
with changes described as in the AC (second bullet point).SetupForm
to conditionally render the components as per the third bullet point in the AC.SetupMain
to check whether thegetSetupFlowMode
selector returnsundefined
to show theProgressBar
.Test Coverage
Visual Regression Changes
QA Brief
ga4setup
feature flag disabled, the Analytics setup should still work the same as before.ga4setup
feature flag enabled:Changelog entry
The text was updated successfully, but these errors were encountered: