Add documentation for new service: check flags:
* validationPeriod
* queryCountThreshold
* queryCountThresholdPercentage
* Remove broken link
* Run prettier
* (op-reg) Clarify that the operation registry is for Enterprise and Team plans.
* (op-reg) Drop the word "grab" and go for something more friendly.
* (op-reg) Add a "What to expect" heads-up on what the installation necessitates.
* op-reg: "should" > "can".
* op-reg: Refer to "Engine" as "Apollo Engine".
* op-reg: Complete sentences with correct words are great.
* Update docs/source/platform/operation-registry.md
* (op-reg) Update for `forbidUnregisteredOperations` predicate function support.
The Apollo Server operation registry plugin — available for Apollo Engine
Team and Enterprise users, now supports passing a predicate function rather
than a boolean on the `forbidUnregisteredOperations` parameter.
This new parameter can be used to selectively enforce the safe-listing
depending on contextual differences — for example, the presence of a header.
This documentation adds the implementation details for that new feature
along with an example of how to utilize it.
* Clarify predicate function with a link.
A predicate function is a function which returns `true` or `false`, which is explained within the same sentence, but a link would be helpful to those who might not understand that terminology. It's worth understanding the term, and a link helps make that easier.
* Address feedback from @peggyrayzis.
Initializers are no longer part of the AC local state API. We're
now recommending that people use `cache.writeData` directly, since
it's already part of the Apollo Cache API and is more flexible.
The location of the `apollo-config` file was moved in
b1204a650c, so this updates the existing references within
this same repository to reflect the new location of the file.
cc @michael-watson
Update some documentation around using the apollo command.
For a new project, service:check will fail, so we should only recommend
that after we know they've published once.
In the 'Set up your development environment' section, there are links to the developer tools and there's a code block for cloning the repo that goes along with this tutorial.
I thought it might be a nice addition to add a link to the GitHub page for the repository in case the reader wants to take a look before cloning it :)
