Test Chartbeat on Lite pages

[amoore108]

Overall changes

• Initial implementation of adding Chartbeat on Lite pages, mainly to test that this approach works and sends data to Chartbeat.

Code changes

• Adds checks for Lite mode and Chartbeat toggle, returning the Canonical Chartbeat component if true
• Adds tests to check that the correct Helmet script tags are added to the page for Lite mode

Testing

1. Visit http://localhost:7080/pidgin/articles/cj5l1958ljjo.lite?renderer_env=live
2. Open the Network tab (may need to refresh the page to see all the transferred files)
3. Confirm that chartbeat.js is downloaded
4. Stay the page for awhile and observe 'ping' requests to Chartbeat
5. Click on one of the 'ping' requests and check that values are present

Helpful Links

Add Links to useful resources related to this PR if applicable.

Coding Standards

Repository use guidelines

[karinathomasbbc]

Here's where the canonical Chartbeat component is added - I was not expecting it to be used here, so wonder if we need to change the logic within UserContext/Chartbeat instead?

is https://github.com/bbc/simorgh/blob/81f36a76c994d60ddc19af17d0dcb14b9df498f9/src/app/contexts/UserContext/Chartbeat/index.tsx

[amoore108]

Tying Chartbeat to the UserContext provider feels a bit strange to me, unless there were historical reasons for doing so?

UserContext handles things like cookies, which makes sense but not sure having Chartbeat in there does? Maybe just saved importing it into individual page components at the time?

[karinathomasbbc]

Yeah that's why I was confused, and wondered if this is an opportunity to try and fix it?

Not sure of the historical reasons, but permission for sending tracking beacons also part of the user context / cookies, and perhaps that's why it was there. But I definitely agree, it doesn't belong within the UserContext, it should be within the Chartbeat Analytics component instead.

[HarveyPeachey]

#3622
NB: the 'UserContext' probably isnt the right place to put this, but as a POC its fine :)

[HarveyPeachey]

Good ol' old tech debt

[karinathomasbbc]

Where's the "old man yells at tech debt" emoji when you need it?!?!?

[HarveyPeachey]

Thinking about this, I guess this was done with client side routing in mind? As the chartbeat config is stored in state, it's probably there to prevent re-renders

[karinathomasbbc]

Haven't we removed client-side / SPA routing functionality? If there's a nicer way to refactor this (i.e. could we move the useState code to the ChartbeatAnalytics component instead of having it in the UserContext?), then we should do it, but if not, it's OK to leave it as is.

[amoore108]

Worth testing actually, as we did encounter some duplication of ATI events when Helmet mounted on the server and re-mounted on clientside hydration.

This would only affect Canonical mind.