Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Fix invalid roles page not displaying #236

Merged
merged 2 commits into from
Sep 17, 2024

Conversation

wjin-lee
Copy link
Member

Fixes unintended behaviour where the a white screen is shown instead of the invalid roles page.

Addressing the "Also" tag:

"Also, refreshing causes you to get stuck on the invalid role page, and doesn’t allow you to move on even if another group member plays through their part (hack is to remove that part from the url but that won’t work for a test class for obvs reasons)."

The invalid roles page does provide a button to attempt to play the scenario again - we essentially bypass the need for a manual browser refresh.

Side note:

  • This PR bundles in a tiny fix to make the thumbnails display correctly on the Assigned scenarios list. Furthermore - assigned scenarios will open the scenario when clicked, instead of giving the option to be edited (which would be an invalid action).

@wjin-lee wjin-lee requested review from harbassan and JordanBlenn and removed request for harbassan September 17, 2024 09:59
@@ -171,14 +171,15 @@ export default function ListContainer({
</ImageListItem>
) : null}
{assignedScenarios && assignedScenarios.length > 0
? assignedScenarios.map(({ _id, name }) => (
? assignedScenarios.map((item) => (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: scenario is better name?

Copy link
Member Author

@wjin-lee wjin-lee Sep 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah - the tricky one here being that item can be a scenario or a scene.

The whole ListComponent shouldn't be the way it is... Ideally the contents are abstracted away, but alas, time is our limiting factor here.

@wjin-lee wjin-lee merged commit d57e9f8 into master Sep 17, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants