-
Notifications
You must be signed in to change notification settings - Fork 23
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
Don't print errors in MDX files #117
Comments
Hmm, I'm confusing. this plugin is notified by Gatsby what files have actually proceeded. @hasparus Do you have GraphQL document snippets in the mdx file? |
yup, I have a pageQuery in MDX file some **markdown**
<Component site={page.data.sitePage} />
export const pageQuery = graphql`
query MusicPageQuery($path: String!) {
sitePage(path: {eq: $path}) {
...TweetDiscussEditLinksDataOnSitePage
}
}
` I'm not sure if my config will be helpful, but I have it public on GitHub right here. |
This should be fixed in v3 ([email protected]) |
rc.0 - implemente XState based scheduler - stabilize schema output - bump GCG - upgrade yarn to v3 - rewritten core logics - upgrade eslint to v8 - upgrade plugin's dependencies - pin graphql version - rewrite emitSchema service - rewriten emitPluginDocument service - rewriten codegen service - add TS & Flow examples rc.1 - skip running on cloud build - fix config validation - more contexture reporting - turn `flattenGeneratedTypesIncludeFragments` true - stabilize documents - change maybe type to use `null` instead of `undefined` - update README rc.2 - add mdx example - MDX example to validate regression of [#117] - update dependencies - added support for `GatsbyImageData` scalar Resolves #40 Resolves #103 Resolves #104 Resolves #109 Fixes #113 Fixes #117 Fixes #120 Resolves #122 Fixes #124 Resolves #131 Fixes #139, #99 Resolves #146 Fixes #157 Fixes #159 Fixes #160 Fixes #161 Fixes #162 Resolves #168 Resolves #169 Fixes #171 [#117]: #117
Howdy 👋
I just encountered this fellow
We couldn't use a generated type in
.mdx
file regardless, so this error seems redundant.Is there a way to specify file extensions in plugin options, so the error doesn't happen?
The text was updated successfully, but these errors were encountered: