Skip to content
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

fix(telemetry): fix isTrackingEnabled always truthy #22613

Merged

Conversation

AhsanAyaz
Copy link
Contributor

Fixed the isTrackingEnabled being exported as a function returning a function instead of a function returning a value

Description

As #22531 mentions, the telemetry module is exporting a function that returns a function instead of a function that returns a boolean value.
I've gone through the entire codebase, we don't use it as a returning function anywhere.

Also, added a minor test for telemetry.js

Documentation

Related Issues

Fixes #22531

Fixed the isTrackingEnabled being exported as a function returning a function instead of a function returning a value
Fixes gatsbyjs#22531
@AhsanAyaz AhsanAyaz requested a review from a team as a code owner March 27, 2020 21:34
@AhsanAyaz
Copy link
Contributor Author

@LekoArts can you review if everything looks fine with this one?

Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, thanks for catching it!

TBF, we still didn't emit any data (we just unnecessarily processed aggregated stats for file sizes in

if (telemetry.isTrackingEnabled()) {
// transform asset size to kB (from bytes) to fit 64 bit to numbers
const bundleSizes = stats
.toJson({ assets: true })
.assets.filter(asset => asset.name.endsWith(`.js`))
.map(asset => asset.size / 1000)
const pageDataSizes = [...store.getState().pageDataStats.values()]
telemetry.addSiteMeasurement(`BUILD_END`, {
bundleStats: telemetry.aggregateStats(bundleSizes),
pageDataStats: telemetry.aggregateStats(pageDataSizes),
queryStats: graphqlRunner.getStats(),
})
}
)

@pieh pieh merged commit 5aaf296 into gatsbyjs:master Mar 31, 2020
@gatsbot
Copy link

gatsbot bot commented Mar 31, 2020

Holy buckets, @AhsanAyaz — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

  1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
  2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

@AhsanAyaz AhsanAyaz deleted the fix/isTrackingEnabled-is-always-truthy branch April 28, 2020 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

gatsby-telemetry "isTrackingEnabled" is always truthy (returns a function)
2 participants