feat(onboarding): hook metrics to the new onboarding #17058
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrainville
requested review from
micieslak,
caybro,
alexjba and
a team
as code owners
Jenkins BuildsClick to see older builds (47)
|
caybro
approved these changes
Jan 13, 2025
|
|
||
| onCurrentItemChanged: { | ||
| if (!!stack.currentItem && !!stack.currentItem.pageName) { | ||
| root.pageNavigated(stack.currentItem.pageName) |
There was a problem hiding this comment.
I think @micieslak just removed the pageName 😆
There was a problem hiding this comment.
Ah, you re-added it... there should be a way to extract it from the class/instance name imo
There was a problem hiding this comment.
The only way I saw to do it was to use stack.currentItem.toString() and then run a regex on it to isolate the class name.
That sounded quite dirty and I read that the format could change from one OS to the other, so I preferred to stick to something that we know will work 100% of the time.
Let me know if there is a way to get it cleanly that I missed.
| @@ -16,6 +16,8 @@ OnboardingPage { | |||
| property alias infoText: infoText | |||
| property alias buttons: buttonsWrapper.children | |||
|
|
|||
| pageName: "KeycardBasePage" | |||
jrainville
force-pushed
the
feat/new-onbaording-integration
branch
from
77b5d44 to
bb284bd
Compare
jrainville
requested review from
dlipicar and
glitchminer
and removed request for
a team
jrainville
force-pushed
the
feat/new-onboarding-metrics
branch
from
dbedf7a to
d2d7fe9
Compare
4 tasks
jrainville
force-pushed
the
feat/new-onbaording-integration
branch
from
bb284bd to
5b2d30f
Compare
jrainville
force-pushed
the
feat/new-onboarding-metrics
branch
from
d2d7fe9 to
0e412d4
Compare
4 tasks
jrainville
force-pushed
the
feat/new-onboarding-metrics
branch
from
0e412d4 to
aa5321c
Compare
jrainville
force-pushed
the
feat/new-onbaording-integration
branch
from
3a0e9b9 to
c13a96b
Compare
glitchminer
approved these changes
Jan 21, 2025
jrainville
force-pushed
the
feat/new-onbaording-integration
branch
from
c13a96b to
8537b0a
Compare
jrainville
force-pushed
the
feat/new-onboarding-metrics
branch
2 times, most recently
from
50391c9 to
476e752
Compare
jrainville
force-pushed
the
feat/new-onboarding-metrics
branch
from
35bea58 to
668777f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does the PR do
Fixes #17047
Hooks the same old metrics we had previously to the new onboarding.
The only difference is we cannot easily track the flow during page navigation because the flow is often jsut sent at the end. Anyway, I think mobile also doesn't give it and it's easy to infer the flow from the page name.
I added a required property to the OnboardinPages so that we cna get the page name and send it. If it's not set on some page, we just don't send a metric.
Affected areas
Onboarding metrics
Architecture compliance
My PR is consistent with this document: Status Desktop Architecture Guide
Impact on end user
None, it works as before
How to test
messageType=AsyncAddCentralizedMetricIfEnabledTaskArg.Risk
Tick one:
The only difference is the pages are not named the same as before, but that's expected since we changed the whole design.