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

[v2] Fix deleteNodes deprecation #4453

Merged
merged 2 commits into from
Mar 13, 2018

Conversation

lettertwo
Copy link
Contributor

When Gatsby prunes stale nodes, it uses the deprecated deleteNodes method, but outside of the context of a plugin, which results in an error when the deprecation warnings are printed.

This PR is divided into two commits; the first fixes the deprecation warning to support this particular scenario, while the second attempts to replace deleteNodes wherever it is used in core.

I'm not sure that the second commit does the right thing, so if it seems wrong, let me know and i can fix or remove it!

@lettertwo lettertwo changed the title Fix deleteNodes deprecation [v2] Fix deleteNodes deprecation Mar 8, 2018
@KyleAMathews
Copy link
Contributor

Thanks! Looks perfect :-)

@KyleAMathews KyleAMathews merged commit 6269d8b into gatsbyjs:v2 Mar 13, 2018
@nihgwu
Copy link
Contributor

nihgwu commented Mar 14, 2018

@KyleAMathews can you release a new version for V2? This breaks my development completely

@KyleAMathews
Copy link
Contributor

New alpha is out.

m-allanson added a commit to m-allanson/gatsby that referenced this pull request Apr 4, 2018
* v2:
  Docgen improvements (gatsbyjs#4757)
  adjust createLocation calls after gatsbyjs#4714 (gatsbyjs#4805)
  Update breaking changes doc
  use basename for router instead of prefixing in link (gatsbyjs#4714)
  Fix inlined styles with path-prefixing (gatsbyjs#4717)
  Publish
  Upgrade & format
  [v2][wip] Upgrade Gatsby v2 to webpack 4 (gatsbyjs#4588)
  fix some jsdoc parsing bits (gatsbyjs#4675)
  [v2] fix wrong merge
  Publish
  Migrate to React Hot Loader v4 (gatsbyjs#4500)
  [v2] Fix deleteNodes deprecation (gatsbyjs#4453)
  Publish
  Switch to latest version of sharp to prevent yarn/npm errors (gatsbyjs#4417)

# Conflicts:
#	packages/gatsby/package.json
#	packages/gatsby/src/utils/webpack-utils.js
#	yarn.lock
@jlengstorf
Copy link
Contributor

Hiya @lettertwo! 👋

This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here.

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 t-shirts and hats, plus some socks that are really razzing our berries right now.)
  2. If you’re not already part of it, we just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again! 💪💜

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.

4 participants