Reduce chances of colliding with absolute path #218
Merged
Conversation
This file contains hidden or 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
✅ Deploy Preview for brittanychiang ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
mechakin
pushed a commit
to mechakin/portfolio
that referenced
this pull request
Oct 16, 2023
Reduce chances of colliding with absolute path
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes #217
This is not a 100% fix to the problem of the absolute path but it should reduce the chances of it happening.
In the meantime, I'll try to find a way to get the relative path instead. The
allMarkdownRemarkdoesn't return the relative path but It's possible to get the relative path using theallFile