Skip to content

Commit

Permalink
docs: add example for disableCorePrefetching (#9852)
Browse files Browse the repository at this point in the history
<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
This closes #9827
  • Loading branch information
TylerBarnes authored and pieh committed Nov 10, 2018
1 parent 0b9d656 commit c725e00
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions packages/gatsby/src/utils/api-browser-docs.js
Expand Up @@ -176,6 +176,8 @@ exports.onPostPrefetchPathname = true
/**
* Plugins can take over prefetching logic. If they do, they should call this
* to disable the now duplicate core prefetching logic.
* @example
* exports.disableCorePrefetching = () => true
*/
exports.disableCorePrefetching = true

Expand Down

0 comments on commit c725e00

Please sign in to comment.