fix: navbar for share modal and end test

[bitfalt]

This PR does the following:

• Make the navbar dissappear when opening the share modal
• User can't finish test if they haven't answered all the questions

Summary by CodeRabbit

• New Features
  • Improved test experience by automatically dismissing error messages after a brief period and preventing submissions when questions remain unanswered.
  • Enhanced share modal behavior by synchronizing its visibility across the app, which dynamically adjusts the interface, such as hiding navigation elements when the modal is active.

[coderabbitai]

Walkthrough

This pull request updates error handling and modal state management across multiple frontend components. In the IdeologyTest component, error messages are now automatically cleared after 3 seconds and a check ensures all questions are answered before submission. The Insights page emits a custom shareModalState event when the share modal's state changes, while the LayoutContent component listens for this event, updates its local state, and conditionally renders navigation accordingly.

Changes

File(s)	Change Summary
frontend/.../ideology-test/page.tsx	Added a useEffect hook to auto-clear error messages after 3 seconds; modified error display logic and added a submission check for unanswered questions.
frontend/.../insights/page.tsx frontend/.../LayoutContent.tsx	Introduced a useEffect hook in Insights to emit a custom shareModalState event; added state management in LayoutContent to listen for this event and conditionally control navigation display and stacking context.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant IT as IdeologyTest
    participant Timer as Timer (useEffect)
    U->>IT: Submit test
    IT->>IT: Validate all questions answered
    alt Unanswered questions
        IT->>IT: Set error state
    end
    IT->>Timer: Initiate timer to clear error
    Timer->>IT: After 3 sec, reset error to null

Loading

sequenceDiagram
    participant I as Insights Page
    participant E as Event System
    participant L as LayoutContent
    I->>E: Emit shareModalState event with current modal state
    E->>L: Deliver shareModalState event
    L->>L: Update isShareModalOpen state
    L->>L: Adjust navigation display based on modal state

Loading

Possibly related PRs

• feat: add ideology test page #68: Focuses on initial error handling improvements in the IdeologyTest component.
• feat: test progress integration and changes in UI #111: Enhances error messaging and progress tracking in the IdeologyTest component.
• Add test logic for ideology quiz  #90: Addresses additional functionality and error handling enhancements within the IdeologyTest component.

Poem

Oh, I’m a code rabbit, with hops so swift and neat,
Errors vanish in a flash — a trick that can’t be beat.
Modal states dance in tune with every event that’s sent,
Navigation hides when modals bloom, that's how our code is meant.
With lines that clear and timers dear, our changes shine so bright!
Hoppin’ in code, under moonlit bytes, through the digital night!
🥕🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b6d5a7e and 25a8a17.

📒 Files selected for processing (3)

• frontend/src/app/ideology-test/page.tsx (3 hunks)
• frontend/src/app/insights/page.tsx (1 hunks)
• frontend/src/components/LayoutContent.tsx (5 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Code Quality & Build
• GitHub Check: Bundle Analysis

🔇 Additional comments (6)

frontend/src/components/LayoutContent.tsx (3)

11-11: LGTM!

The imports are correctly added for the new state management functionality.

---

31-81: LGTM!

The implementation is well-structured:

• State management is properly initialized
• Event listener is correctly set up with cleanup
• Custom event handling follows best practices

---

126-132: LGTM!

The changes effectively implement the navbar visibility requirement:

• Navigation is hidden when share modal is open
• Z-index ensures proper layering of components

Also applies to: 141-141

frontend/src/app/ideology-test/page.tsx (2)

35-44: LGTM!

The error auto-clearing implementation is well-designed:

• Uses proper cleanup to prevent memory leaks
• 3-second timeout provides good user experience

---

94-104: LGTM!

The end test validation is effectively implemented:

• Ensures all questions are answered before submission
• Provides clear feedback to users through error messages
• UI presentation of errors is well-structured

Also applies to: 325-329

frontend/src/app/insights/page.tsx (1)

41-47: LGTM!

The share modal state event emission is well-implemented:

• Correctly syncs modal state across components
• Event payload structure is appropriate
• Implementation follows React best practices

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[netlify]

✅ Deploy Preview for lucent-florentine-971919 ready!

Name	Link
🔨 Latest commit	25a8a17
🔍 Latest deploy log	https://app.netlify.com/sites/lucent-florentine-971919/deploys/67abf638e9fd940008c65466
😎 Deploy Preview	https://deploy-preview-146--lucent-florentine-971919.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.