Video atom livestream

[abeddow91]

What does this change?

This PR centralises the logic used to determine whether a YouTube video atom represents a livestream.

It introduces a new isLive property on the YouTube atom model and moves the logic that derives this value into the enhanceCards step. Downstream consumers of the atom can now rely on this single, explicit field instead of re-implementing their own checks.

Why?

DCR currently relies on brittle logic to infer whether a YouTube video is a livestream - specifically by checking whether the video duration is 0. This logic is made even more brittle as any youtube video without a duration is defaulted to 0 during enhancement.

Ideally, this decision should be made further upstream in Media Atom Maker when the atom is uploaded to YouTube. Until that is possible, this PR refactors the existing behaviour to:

• Centralise the livestream decision in one place
• Make the intent explicit via an isLive property
• Reduce duplication and fragility in downstream code

Note: This change does not improve the underlying detection logic itself. The duration based check remains for now, but it is now isolated and easier to replace in the future once a more reliable signal is available.

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

[domlander]

Looks great. I think this is a really useful PR.

• Should we use either isLive or isLiveStream in both places or do you think there's enough semantic difference between the words to make them suitable for Card.tsx and YoutubeBlockComponent.importable.tsx respectively?

[abeddow91]

Looks great. I think this is a really useful PR.

• Should we use either isLive or isLiveStream in both places or do you think there's enough semantic difference between the words to make them suitable for Card.tsx and YoutubeBlockComponent.importable.tsx respectively?

Thanks @domlander. Good point - I dont think there is a distinction between the two so I've opted for isLive everywhere 👍 That should make debugging simpler.

[github-actions]

Deploy build 24495 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 24495 of dotcom:rendering-all to CODE
• Deploy parts of build 24495 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Deploy build 664 of dotcom:ab-testing to CODE

All deployment options

• Deploy build 664 of dotcom:ab-testing to CODE
• Deploy parts of build 664 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[gu-prout]

Seen on PROD (merged by @abeddow91 8 minutes and 32 seconds ago) Please check your changes!