slugs for foreign keys #33
Open
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.
Problem
Advances #27 and #7 Closes #18
Solution
Ongoing work on schema typing, resolvers, and relationships between entities in gatsby's data layer.
The focus of this pr is making this work:
dataset: MarkdownRemark @link(by: "fields.slug")The idea is to have a foreign key relationship where one markdown file references another by its slug.
This takes a little bit more work than using the raw string from
frontmatter.namebut it makes the relationships less brittle. Because the slugs are/directory/filenamethey are far less likely to run into namespace collisions than a field linename.Attendant to this I added:
slugifyas a dependency to help with slugsvitestand one test suit for the resolver utils