You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(gatsby-source-drupal): Use the collection count from JSON:API extras to enable parallel API requests for cold builds (#32883)
* feat(gatsby-source-drupal): Use the collection count from JSON:API extras to construct URLs
Otherwise, we have to wait to start querying each page until the previous one finishes. This change
lets us query all pages in parallel. So instead of fetching one collection page at a time, we can fetch up to the maximum concurrency (default 20).
For a test site with ~3200 entities, this PR dropped sourcing time from ~14s to 4s.
* use new browser-based URL parser
* Comment code more
* Use the page size the site has set instead of assuming 50
* Use the original type that's set as that's always there
* Log out updates while sourcing
* Encourage people to enable this setting in the README
* Update gatsby-node.js
You can use the `filters` option to limit the data that is retrieved from Drupal. Filters are applied per JSON API collection. You can use any [valid JSON API filter query](https://www.drupal.org/docs/8/modules/jsonapi/filtering). For large data sets this can reduce the build time of your application by allowing Gatsby to skip content you'll never use.
0 commit comments