What example does this report relate to?

with-Apollo

What version of Next.js are you using?

10.0.0

What version of Node.js are you using?

10.14.2

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

Other platform

Describe the Bug

The Apollo client query response is s

Is your feature request related to a problem? Please describe.
The search functionality does not work for our content. It hits the GitHub API limit after 2 searches. see https://answers.netlify.com/t/cms-search-hitting-github-api-limit/39124

Describe the solution you'd like

1. A configuration option to disable search entirely so our users don't hit the API limit
   This should be p

As we attempt to pick up the release cadence, we are in need of an explicit changelog file which enumerates changes in each version. This should be a markdown or plaintext file adhering to some form of standardized format. Ideally, it will be able to work with #582.

There are 3 "examples" for dynamic (client side) routing, 2 in the docs (guides) and one is a template.

The 2 guides in the docs are technically working, but they do not use addPrefetchExcludes.

• dynamic-routes-reach-router.md
• [docs/guides/dynamic-rou

The main issue is that it's painful to get a real library loaded without just creating some files and commit them. Ideally there would be a function/macro that can be used to create pages/sections.
The other files in the library component create whatever is needed manually but it makes tests very verbose/long where 90% of the test is actually setup.
The library.rs really needs some more tes

• I've read the [contribution guidelines][1] and agree with them

I've found a bug and checked that ...

• ... the problem doesn't occur with the default MkDocs template
• ... the problem is not in any of my customizations (CSS, JS, template)
• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related t

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo