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.

Sign up for GitHub

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

Update migrating-from-v1-to-v2.md #8302

Merged
merged 1 commit into from
Sep 19, 2018
Merged

Update migrating-from-v1-to-v2.md #8302

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update migrating-from-v1-to-v2.md 
Added a note around possible wrong import of `graphql` from the `graphql` package instead of `gatsby`. I was bitten by this badly and took more than an hour to figure out!
  • Loading branch information
@pavanpodila
pavanpodila authored Sep 19, 2018
commit ec442c835ffbb417ed40035f27cac73016ce4b24
2 changes: 2 additions & 0 deletions docs/docs/migrating-from-v1-to-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -744,6 +744,8 @@ export const query = graphql`

> There is a codemod that can automatically make this change to your projects. Check out the [`gatsby-codemods`](https://www.npmjs.com/package/gatsby-codemods) package for usage instructions.

> Note that if you are relying on the auto-import feature of WebStorm or VSCode, it may import `graphql` from `'graphql'` instead of `'gatsby'`. This will throw a bunch of errors around bad imports. Make sure `graphql` is always imported from `gatsby`.

### Rename `boundActionCreators` to `actions`

`boundActionCreators` is deprecated in v2. You can continue using it, but it’s recommended that you rename it to `actions`.
Expand Down