Slug source not resolving references
See original GitHub issueIs your feature request related to a problem? Please describe. N/A
Describe the solution you’d like References should be resolved in the slugify source, e.g.
source: doc => `flights-from-${doc.title}-${doc.origin.name}`
Describe alternatives you’ve considered Implementing a slugify function that resolves the references.
Additional context N/A
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Slug - Sanity.io
A schema type for slugs, typically used to create unique URLs. A slug is a unique string (typically a normalized version of title...
Read more >Gatsby slug broken - Stack Overflow
But when I copy and paste the url of the blog to go there directly, the content will not load. Just the template...
Read more >Common Errors - Welcome to Whalesync
If you map the slug field, you will need to ensure you have valid values in that field. Slugs cannot be empty, have...
Read more >What the Heck are Content Slugs and How Do I Use Them?
The slug helps resolve this problem by allowing a human readable (and frequently user generated) identifier for a piece of content.
Read more >Slug Compiler | Heroku Dev Center
Art sources (like .psd files); Design documents (like .pdf files) ... Heroku CI users: Do not list your test directory in .slugignore ....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks again for reporting! This was fixed in v1.148.6 which was just released 😃
Thanks for the solution. I definitely think this should go into the docs on the website as an example!