allow processing of custom markdown nodes #46
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
in case you created markdown nodes programmatically (e.g. since you want to process markdown content in frontmatter fields), you can now provide a custom resolver function that calculates the correct path for the markdown content. Fixes danielmahon#43
|
anyone home? |
|
Does this resolve the famous "Field “image” must not have a selection since type “String” has no subfields" because I think I have tried absolutely everything. It worked sporadically with [email protected]" but not at all with v2 |
|
@dancingMonkey dont think this is related, however, I am not sure which problem you are referring to. Yours sounds like a wrong query. This patch will rewrite image urls in frontmatter markdown fields. |
A little bit late but you are right, got it fixed. Messed up the gatsby-config🤔😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
in case you created markdown nodes programmatically
(e.g. since you want to process markdown content in frontmatter fields),
you can now provide a custom resolver function that calculates the correct path for the markdown content.
Fixes #43