-
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
fix(gatsby): Validate sub plugins options #37804
Merged
pieh
merged 3 commits into
gatsbyjs:master
from
Talaxy009:fix/validate-sub-plugins-options
Mar 30, 2023
Merged
fix(gatsby): Validate sub plugins options #37804
pieh
merged 3 commits into
gatsbyjs:master
from
Talaxy009:fix/validate-sub-plugins-options
Mar 30, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gatsbot
bot
added
the
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
label
Mar 29, 2023
pieh
added
topic: core
Relates to Gatsby's core (e.g. page loading, reporter, state machine)
topic: remark/mdx
Related to Markdown, remark & MDX ecosystem
and removed
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
labels
Mar 30, 2023
Hey @Talaxy009 - I massaged your PR a bit not to hardcode
|
@pieh Got it, thanks for optimizing |
LekoArts
approved these changes
Mar 30, 2023
LekoArts
changed the title
fix(gatsby): validate sub plugins options of gatsby-plugin-mdx
fix(gatsby): Validate sub plugins options
Mar 30, 2023
This is now available in |
TylerBarnes
pushed a commit
that referenced
this pull request
Mar 30, 2023
* fix(gatsby): validate sub plugins options of gatsby-plugin-mdx * revert hardcoded path to subplugins * validate subplugins if they are not under 'options.plugins' field --------- Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
pieh
added a commit
that referenced
this pull request
Apr 18, 2023
* add touch nodes optout action * cleanup * start adding backreference cache * revert formatting * remove unused variable * remove unused var * switch from opting out types from stale nodes to opting out entire plugin * add no nodes warning * fix bug where double bound actions are ignored when there are no args * update progress mock * get owner from plugin * rename type * rename types * use redux types instead of pulling from lmdb * remove unused line * Update source-nodes.ts * use CREATE_NODE action instead of adding a new type owner action * add typeowners test * test touchNodes and enableStatefulSourceNodes() * fix contentful tests * snapshot updates * chore(changelogs): update changelogs (#37808) * fix(deps): update starters and examples - gatsby to ^5.8.1 (#37806) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(gatsby): Validate sub plugins options (#37804) * fix(gatsby): validate sub plugins options of gatsby-plugin-mdx * revert hardcoded path to subplugins * validate subplugins if they are not under 'options.plugins' field --------- Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com> * fix(create-gatsby): Use correct name in summary message (#37809) * actual fix * other misc changes * chore(release): Publish next - create-gatsby@3.9.0-next.1 - gatsby-cli@5.9.0-next.1 - gatsby-plugin-sharp@5.9.0-next.1 - gatsby-transformer-sqip@5.9.0-next.1 - gatsby@5.9.0-next.2 * remove testing timeout * minimal docs * reword * add comment * reportOnce instead of throwing an error * consolidate typeOwners * use new typesToPlugins Map keys instead of pluginsToTypes Map values * consolidate remaining typeOwners object checks into new typeOwners reducer * fix missing owner error * fix type errors and incorrect plugin object reference * maybe fix unit tests * make SitePage nodes owned by internal-data-bridge * add missing fields on some TOUCH_NODE actions * skip owner checks when deleting child nodes * sp * Update yarn.lock * reduce memory usage by storing minimal backreference info and not blocking the event loop * remove coment * remove extra logs * add helper to explain what the setImmediate promise is for * remove unneeded entryNode condition * refactor createAssetNodes to use async/await * add cached node counts by assets vs content * refactor to fix linting failure * fix tests * ensure mutated existing node data is applied during updates * restore previous logging behaviour * fix test state * always reset memory node count when existingNodes is empty * revert more logging * update test to use new createAssetNodes changes * store count instead of huge set of id's to use less memory * remove debugger * make sure sys.type exists before checking * move enableStatefulSourceNodes call to main sourceNodes fn * use util * fix e2e test - ContentfulTag node doesn't have sys.type * always exclude ContentfulTag nodes from memory Map cache * fix linting (consistent return) --------- Co-authored-by: GatsbyJS Bot <core-team@gatsbyjs.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Taozc <41264828+Talaxy009@users.noreply.github.com> Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com> Co-authored-by: Lennart <lekoarts@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
topic: core
Relates to Gatsby's core (e.g. page loading, reporter, state machine)
topic: remark/mdx
Related to Markdown, remark & MDX ecosystem
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The gatsby-plugin-mdx uses
gatsbyRemarkPlugins
as its sub plugin key, but gatsby only checks for theplugins
key, which causes issue #37792 .Related Issues
Fixes #37792