Skip to content
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.

Configuration option to remove page listing from developer 404 page #30

Closed
wants to merge 1 commit into from
Closed

Configuration option to remove page listing from developer 404 page #30

wants to merge 1 commit into from

Conversation

kevee
Copy link

@kevee kevee commented Feb 13, 2019

We have been running into issues where sites with over 100,000 pages cause the developer 404 page to either stop, or consume a lot of resources. This simple RFP adds a configuration variable to remove that listing.

Not sure if this warrants an entire RFC. 🤷‍♀️

@pieh
Copy link

pieh commented Feb 13, 2019

Maybe instead of config flag we could adjust dev 404 page:

  • set fixed limit on displayed pages info (100 or so)
  • add "show more" button / number input to override default one
  • add filter input

@KyleAMathews
Copy link
Contributor

@pieh can loki do basic search? Adding the filtering support into graphql directly would be nice

@kevee
Copy link
Author

kevee commented Apr 12, 2019

@pieh @KyleAMathews I found that even just doing a splice would fix the problem and adding simple pagination - the issue I'm finding with a site that has well over 500k pages is that just the DOM work is what's dragging it down.

I have a feature branch ready to pull - do you want a PR or should this be discussed further in the RFC?
https://github.com/kevee/gatsby/tree/feature/limited-404-page

@stefanprobst
Copy link

Related: gatsbyjs/gatsby#13204

@KyleAMathews
Copy link
Contributor

This got merged so I'm going to close this RFC gatsbyjs/gatsby#13344

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants