feat(SLB-512) Taxonomy filters content hub #391
Conversation
| @@ -0,0 +1,8 @@ | |||
| query ContentHubTerms { | |||
There was a problem hiding this comment.
By adding this one as a static query and injecting it as an executor, the options could be fetched at build time and appear immediately when the page is opened. It should work the same way as the FrameQuery in layout.tsx:
silverback-template/apps/website/src/layouts/index.tsx
Lines 13 to 18 in 288a886
| @@ -451,6 +501,9 @@ type Query { | |||
|
|
|||
| stringTranslations: [TranslatableString!] | |||
| @gatsbyNodes(type: "TranslatableString") | |||
|
|
|||
| contentHubTerms: TermContentHubResults! | |||
| @loadByVocabulary(bundle: "content_hub") | |||
There was a problem hiding this comment.
To make the above work, this would have to use @gatsbyNodes as well, so Gatsby knows about content hub terms.
| """ | ||
| Content Hub Terms Results from query | ||
| """ | ||
| type TermContentHubResults |
There was a problem hiding this comment.
Is this type required? Couldn't the Query.contentHubTerms field directly output [TermContentHub].
| } | ||
|
|
||
| return [ | ||
| 'total' => count($items), |
There was a problem hiding this comment.
If the other changes are applied, we would also emit just the list of items directly, and no wrapping result opject.
Description of changes
Adding and exposing taxonomy filters onto the content hub.
Motivation and context
To create better filtering for content.
How has this been tested?