Resolve file paths in node fields #26
Merged
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
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.
This PR resolves all relative file paths in node fields. It also makes it possible to resolve absolute paths with a
resolveAbsolutePathsoption. That will make Gridsome able to process image paths from Netlify CMS etc.When a field contains
/images/image.png, Gridsome normally assumes the image is located in/static/images/*and leave the field as is, since they will be copied during deployment. But Gridsome will convert the field into an absolute file path resolved from the root folder ifresolveAbsolutePathsistrue. Your images should be located at{root}/images/*. The option can also take an absolute path to a folder containing the referenced files.It also works for urls. Absolute pathnames like
/image.jpgconverts into absolute urls whenresolveAbsolutePathsistrue.