-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
boundActionCreators warning should say to replace them with "actions" and also link to the upgrade docs for this #6825
Comments
@KyleAMathews: I updated this from a card to an issue so that it could be moved into the appropriate sub-epic. |
We should link to https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/#rename-boundactioncreators-to-actions in the error message. The error message is generated here: gatsby/packages/gatsby/src/commands/develop.js Lines 388 to 421 in b6bdb82
I think we can modify it a bit: const fixMap = {
boundActionCreators: {
newName: `actions`,
docsLink: `https://next.gatsbyjs.org/docs/migrating-from-v1-to-v2/#rename-boundactioncreators-to-actions`,
},
// ...
} And then update the print template to show that docs link as well. This would be a great first issue for someone! |
Hi, I'm new here and I'd love to take this! |
Yes! Thanks @thefifthisa! Let us know if you have questions or need a second set of eyes. 💪💜 |
@jlengstorf Just opened a PR! Please let me know what I need to change or if it's okay already. |
The "boundActionCreators" API is deprecated and replaced with "action" as mentioned here: gatsbyjs/gatsby#6825. To avoid "breaking changes" for those still using GatsbyJS v1, I have not removed the boundActionCreators in the parameter list. It's up to you to make the final decision.
boundActionCreators warning should say to replace them with "actions" and also link to the upgrade docs for this
The text was updated successfully, but these errors were encountered: