feat: Add links to different studio screens and add a multiview for development and testing

[rjmunro]

About the Contributor

Type of Contribution

This is a Feature

Current Behavior

If you start at the URL of, for example, a directors screen (e.g. http://localhost:3005/countdowns/studio0/director) and go up a level (e.g. http://localhost:3005/countdowns/studio0/), it would redirect you to the home page of Sofie. Also there are several available views for a studio (Presenter Screen, Director Screen, Overlay Screen, Camera Screen
Prompter, Active Rundown and it's hard to remember them all

New Behavior

If you go to a URL like http://localhost:3005/countdowns/studio0/ you get a list of the main views available:

I've also made a multiView which shows most of them all in iframes, which is great for testing.

Currently this page is not itself listed anywhere. A page should be added to enumerate all the available studios and link to these views. But we may want to move some things around and add some redirects first because having most of these views under /countdowns/ possibly doesn't make sense.

Testing

• I have added one or more unit tests for this PR
• I have updated the relevant unit tests
• No unit test changes are needed for this PR

Affected areas

This PR adds a couple of per-studio pages, neither of which has any active code, just links to already existing pages.

Time Frame

• Not urgent, but we would like to get this merged into the in-development release.

Status

• PR is ready to be reviewed.
• The functionality has been tested by the author.
• Relevant unit tests has been added / updated.
• Relevant documentation (code comments, system documentation) has been added / updated.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[nytamin]

Quality Gate failed

Failed conditions 0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

Please ignore Sonar's issue with Code Coverage in this PR (we're in the process of tuning it).

[jstarpl]

I don't see any particular problems, but I do see that while there's a header on the main "countdowns landing page":

There is none if I go to a non-existant countdown variant, but I still get the list:

It's not a big thing, but I think it would be nice if we either kept the fallback redirect, in case someone opens a page that doesn't exist, or have the header always if our new policy is to show this page now for anything starting with /countdowns.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[rjmunro]

@jstarpl

I don't see any particular problems, but I do see that while there's a header on the main "countdowns landing page":

It's not a big thing, but I think it would be nice if we either kept the fallback redirect, in case someone opens a page that doesn't exist, or have the header always if our new policy is to show this page now for anything starting with /countdowns.

I've made the routes exact only and added a pseudo-404 page.