-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: track a user navigating backwards through flow by node id #2357
Conversation
…tton and store target node data - Users can navigate backwards through a flow to a specific node via the back or change buttons - On click of back or change track the initiator and some metadata of target node by updating the analytics log
14fdad3
to
aa669d4
Compare
const targetNodeMetadata = getTitleAndTypeFromFlow(nodeId); | ||
console.log("Target node info: ", targetNodeMetadata); | ||
const metadata: Record<string, NodeMetadata> = {}; | ||
metadata[`${initiator}`] = targetNodeMetadata; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opted for this syntax as I was getting errors that the initiator
wasn't being used when I was trying to apply is a key in the object creation.
Removed vultr server and associated DNS entries |
1 similar comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies it's taken me awhile to properly get to this one, all working as expected on pizza for me and tracking "back" and "change" from both Result & Review 🙌
Feels like a simple structure to extend in the future like you mention for section navigation and "overrides" 💯
initiator: BackwardsNaviagtionInitiatorType, | ||
) { | ||
const targetNodeMetadata = getTitleAndTypeFromFlow(nodeId); | ||
console.log("Target node info: ", targetNodeMetadata); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: looks like this console.log
might be a remnant of local dev and can be dropped before merging? one more below on L318 too
- As per #2357 (comment) - Remove unecessary logs
What
back
orchange
button.back
orchange
and store target node metadata i.e.title
andtype
.Why
back
orchange
button.Screen Recording
Screen.Recording.2023-11-02.at.12.54.42.mov