-
Notifications
You must be signed in to change notification settings - Fork 7
fix(glean): rename events to use kebab case #68
Conversation
@@ -52,7 +52,7 @@ function previewAvatar() { | |||
} | |||
|
|||
async function toggleNotifications() { | |||
const dataGlean = relationship?.notifying ? 'profile.notify_stop' : 'profile.notify_start' | |||
const dataGlean = relationship?.notifying ? 'profile.notify.stop' : 'profile.notify.start' |
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.
These events were renamed to include the .
separation between notify
and the action (start
or stop
)
@@ -23,7 +23,7 @@ const { client } = $(useMasto()) | |||
const useStarFavoriteIcon = usePreferences('useStarFavoriteIcon') | |||
const { share, isSupported: isShareSupported } = useShare() | |||
|
|||
function recordEngagement(dataGlean) { | |||
function recordEngagement(dataGlean: string) { |
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.
Added a type here to make vscode happy
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.
Hmm my vscode doesn't get sad over this. Do you have any idea what the difference is in our IDEs?
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.
Not sure. I thought maybe I had a typescript extension on in vscode, but apparently I don't. Do you have one?
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 disabled some extension with the word TypeScript in it that I couldn't find in the marketplace, and then I updated my IDE. Now I'm getting the error. Not sure which of the two was the culprit though
While reviewing #67 I noticed that we had a mix of cases when it came to naming our engagement events, so I reached out to the data analytics team to see if they had a preference. They decided on
kebab-case
, so this PR simply updates the existing engagement events, plus those in #67, to be consistent. Two other small changes called out in comments.This PR is to be merged into #67.