guardian / guardian/tagmanager

use the "hidden" flag to control whether a tag is selectable in Composer UI (and others?)

Open
#592 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
13
Forks
6
Avg merge
6m
Merged PRs (30d)
1

Description

Tags have a boolean property called "hidden" that can be set in the TagManager UI, but has no effect elsewhere. It seems to be a legacy property from r2. see [#6009](https://github.com/guardian/flexible-content/issues/6009)

We want to re-purpose this flag to prevent "hidden" tags appearing in the UI so users cannot attach them to content. This will mostly be relevant for the obsolete commissioning tags that need to exist, but not be added to nee content.

Currently, the property is exposed in the internal tag manager API only, but not the tag manager hypermedia API consumed by workflow-frontend, composer and media-atom maker - the likely first step would be to add the "hidden" property to the model exposed on the hypermedia API

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the Tag Manager hypermedia API model and compare it with the internal Tag Manager API, then check how workflow-frontend, Composer, and media-atom maker consume tags. The work is done when the hidden property is exposed through the hypermedia API and hidden tags no longer appear as selectable tags in the relevant UIs.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.