Skip to content

Commit

Permalink
Update docs/docs/configuring-usage-with-plugin-options.md
Browse files Browse the repository at this point in the history
Co-authored-by: Megan Sullivan <megan@gatsbyjs.com>
  • Loading branch information
mxstbr and meganesu authored Oct 15, 2020
1 parent 5b71463 commit f0d6ad8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/docs/configuring-usage-with-plugin-options.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ The following table lists possible options values and an example plugin that mak

## How to validate options

In order to make configuration easier for users, plugins can optionally define a [Joi](https://joi.dev) schema to enforce data types for each option using the [`pluginOptionsSchema` API](/docs/node-apis/#pluginOptionsSchema) in `gatsby-node.js`. Gatsby validates that the options users of the plugin pass to it match the schema.
In order to make configuration easier for users, plugins can optionally define a [Joi](https://joi.dev) schema to enforce data types for each option using the [`pluginOptionsSchema` API](/docs/node-apis/#pluginOptionsSchema) in `gatsby-node.js`. When users of the plugin pass in configuration options, Gatsby will validate that the options match the schema.

For example, here is what the schema for `gatsby-plugin-console-log` looks like:

Expand Down

0 comments on commit f0d6ad8

Please sign in to comment.