Ag/more tag params

[fredex42]

What does this change?

Adds some more tag search parameters, hopefully to help Ask Guardian! 🤞

• Fuzzy-matching on the tag name
• Matching on tag categories and references
• Return of matching documents in a sub-query on tags

How to test

• Deploy to CODE
• Fire it up on https://graphiql.capi.code.dev-gutools.co.uk/
• Make sure you refresh the schema
• Build a tag query like this: (note the deliberate mis-spelling of "football")

{
	tag(q:"footbowl",type:keyword,limit:5) {
    totalCount
    endCursor
    nodes {
      webTitle
      id
      internalName
    }
    matching_content(limit:10, orderDate:published, orderBy:newest, excludeTags:["politics/politics"]) {
      totalCount
      endCursor
      nodes {
        id
        webTitle
        keywords:tags(type:keyword) {
          id
        }
      }
    }
  }
}

You should get matching tags for Football, katine/football, Women's Football, Fantasy Football....

Also, you should get a ton of hits in matching_content which can be paginated through by taking the endCursor value and putting it into a cursor: parameter in the matchingContent query.

• Have a play with the different options

To Do

• Fix cursor pagination for tags
• Add a selector for content matching each single tag (on the Tag object)

How can we measure success?

Another way of exploring Guardian content

Have we considered potential risks?

Keep an eye on query complexity

[github-actions]

Deploy build 46 of Content Platforms::concierge-graphql-experimental to CODE

All deployment options

• Deploy build 46 of Content Platforms::concierge-graphql-experimental to CODE
• Deploy parts of build 46 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Unit Test Results

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 96d0bbb. ± Comparison against base commit dd1d0d1.

♻️ This comment has been updated with latest results.