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

Describe the bug
The "Add" button, allowing to add a new item in a list object, have a hard-coded text, so it's not possible to translate.

Expected behavior
Allow translation of the button.

Screenshots
I am using the French translation, but the button is in English :
![image](https://user-images.githubusercontent.com/11643685/120892928-cada1b80-c610-11eb-82a0-5253b89253e4.png

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

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