Relational URL pattern
See original GitHub issueFeature request
Summary
Allow querying relational fields in the URL pattern like /prefix/[relation.slug_field]
.
Why is it needed?
For better dynamic URL patterns.
Related issue(s)/PR(s)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Understand Default URL Pattern - Contentstack
Understand Default URL Pattern · Prefix URL: Denotes the path where the entry resides. For example, /seo/blog · Entry-specific URL: Denotes the URL...
Read more >HTML and URLs
Its path generally refers to a resource on the same machine as the current document. Relative URLs may contain relative path components (".."...
Read more >URL Pattern API - MDN Web Docs
The URL Pattern API defines a syntax that is used to create URL pattern matchers. These patterns can be matched against URLs or...
Read more >URLPattern brings routing to the web platform
At its heart, routing involves taking a URL, applying some pattern matching or other app-specific logic to it, and then, usually, ...
Read more >Absolute urls, relative urls, and...? - Stack Overflow
An absolute URL contains all the information necessary to locate a resource. A relative URL locates a resource using an absolute URL as...
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
The feature is in beta. You can install it like this:
yarn add strapi-plugin-sitemap@beta or npm install strapi-plugin-sitemap@beta
@boazpoolman Just bumping this, any chance we can see this update move forward for components?