From 286133a8b4c58b8b9822622baf7a6d29bb1f28b8 Mon Sep 17 00:00:00 2001 From: Can Rau Date: Thu, 18 Apr 2019 03:45:17 -0500 Subject: [PATCH] docs: Remove note about stringified options MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I'm not entirely sure about this, I'm aware of the origin https://github.com/gatsbyjs/gatsby/pull/3987 yet this PR I made proofs the opposite https://github.com/gatsbyjs/gatsby/pull/12060 Only thing I can think of right now that browser APIs get stringified, couldn't verify this so far, this https://github.com/gatsbyjs/gatsby/issues/3834 is suggesting they get stringified and it's the reason the note was added to the docs in the first place.. Couldn't just leave my confusion alone and thought doing it in a PR might be useful if it's actually not valid anymore so it can be merged directly, otherwise feel free to reject it of course 👍 --- docs/docs/plugins.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/docs/plugins.md b/docs/docs/plugins.md index b150b5b02a9a7..6b094df6cd01b 100644 --- a/docs/docs/plugins.md +++ b/docs/docs/plugins.md @@ -78,8 +78,6 @@ module.exports = { } ``` -Note that plugin options will be stringified by Gatsby, so they cannot be functions. - ## Loading plugins from your local plugins folder Gatsby can also load plugins from the your local website plugins folder which is a folder named `plugins` in the website's root directory.