-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Remove note about stringified options #13440
Conversation
I'm not entirely sure about this, I'm aware of the origin #3987 yet this PR I made proofs the opposite #12060 Only thing I can think of right now that browser APIs get stringified, couldn't verify this so far, this #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 👍
Browser APIs options get JSON.stringified ( gatsby/packages/gatsby/src/bootstrap/index.js Line 313 in 9f0835a
and SSR APIs options get JSON.stringified ( gatsby/packages/gatsby/src/bootstrap/index.js Line 333 in 9f0835a
Node APIs are not getting stringified because they executed in the same context, so they are just used from memory as they are |
Okay, good to know, thanks for clarifying 🙏
But maybe it's not the right place 🤔 I think it's a little bit misleading as they can be in certain cases.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to pass function for |
I think it is worth mentioning somewhere in the plugin docs too. I don't know in which section it would fix through |
I'm not entirely sure about this, I'm aware of the origin #3987 yet this PR I made proofs the opposite #12060
Only thing I can think of right now that browser APIs get stringified, couldn't verify this so far, this #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 👍
Description
Related Issues