Fix maximized code navigation

[NicholasMy]

This fixes a very niche bug discovered by a professor at UB that hindered viewing student submissions.

Motivation and Context

Prior to this fix, if you maximized the code view from a submission and then refreshed the page, it wouldn't load properly due to a JavaScript exception. You would need to reset the layout before being able to view any submissions.

Description

I used a technique from a similar issue I found at golden-layout/golden-layout#253 (comment), where we only call toConfig if the layout has been fully initialized. This prevents the exception from being raised and allows the page to load properly.

How Has This Been Tested?

After making these changes, I opened a student's submission and maximized the code view. I refreshed the page and verified it loaded properly and preserved my maximized layout. I reset the layout and verified it behaved how I'd expect.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have run rubocop and erblint for style check. If you haven't, run overcommit --install && overcommit --sign to use pre-commit hook for linting
• My change requires a change to the documentation, which is located at Autolab Docs
• I have updated the documentation accordingly, included in this PR

Summary by CodeRabbit

• Bug Fixes
  • Improved stability by ensuring layout state is saved only when the layout is initialized.

[coderabbitai]

Walkthrough

Walkthrough

This update introduces a conditional check to ensure the layout state is saved to localStorage only if the layout is initialized. This change aims to prevent potential issues that could arise from attempting to save an uninitialized layout state.

Changes

File Path	Change Summary
app/views/submissions/_golden-layout.html.erb	Added a conditional check if (myLayout.isInitialised) before saving the layout state to localStorage.

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dd086c8 and 7f4fb82.

Files selected for processing (1)

• app/views/submissions/_golden-layout.html.erb (1 hunks)

Files skipped from review due to trivial changes (1)

• app/views/submissions/_golden-layout.html.erb

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[damianhxy]

LGTM, thanks for the fix!

Before

Also, various javascript features such as adding annotations do not work.

After

[epicseven-cup]

Thank you @NicholasMy for the fix