To prep for share/remix, we needed to load some level data for standalone levels. Previously we did not load any level data for standalone levels, and just loaded projects based on the channel id passed through app options. We still want to load the project based on that channel id, but also want to get level properties for the standalone level, as the level configuration contains information about share and remix headers. There is still one case where we load a project and never care about level data, which is /projectbeats.

In this PR I updated the thunks for setting up a lab a bit. What was previously setUpForLevel is now setUpWithLevel, and takes an optional channel id. We will load level properties as before, but then create our project manager either based on the channel id if it exists, or based on the level and script if it does not.

What was previously loadProject is now setUpWithoutLevel (to make things clearer). Previously we set up the project manager outside of this method, to make the methods more unified I moved that logic into this thunk, and then loaded the project as before. I also added the logic to cleanup any existing project manager, so if we want to use this in a page that switches projects without reloading from the server we can.

I also added a couple useful level properties to lab redux, hideShareAndRemix and isProjectLevel, which will be used in the upcoming share and remix work.

Links

• jira ticket: SL-808

Testing story

Tested locally that an allthethings level, a standalone project, and /projectbeats still work.

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked