Fix: Remove unused props variable in BooleanTable.vue

[s1dhu98]

Destructured the props in the setup script to avoid the ESLint unused variable warning. The props are used directly in the template.

Summary by CodeRabbit

• Bug Fixes

  • Stabilized rendering of message notification lists with explicit keys

• Style

  • Reformatted component markup and attribute ordering for readability
  • Cosmetic HTML/formatting tweaks across several panels and inputs

• Chores

  • Tightened mobile UI visibility controls for simulator views
  • Removed debug logging from authentication handlers
  • Clarified component prop declarations with explicit types and defaults

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	b384bc2
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/697e126ad0e7a700071a9716
😎 Deploy Preview	https://deploy-preview-900--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 45 (🔴 down 4 from production) Accessibility: 73 (no change from production) Best Practices: 92 (no change from production) SEO: 82 (no change from production) PWA: - View the detailed breakdown and full score reports

---

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

[coderabbitai]

Warning

Rate limit exceeded

@s1dhu98 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 12 minutes and 37 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

This PR makes localized, non-behavioral changes across several Vue components: BooleanTable.vue replaces a direct defineProps usage with a typed, destructured withDefaults(defineProps<...>(), {...}) pattern and adds a JSDoc/import; Extra.vue adds :key to v-for loops, reformats markup, and tightens multiple mobile-related v-if guards; UserMenu.vue removes a console.log debug statement; TestBenchPanel.vue, TimingDiagramPanel.vue, and TimingDiagramMobile.vue apply attribute reordering and formatting changes without altering logic or event handlers.

Possibly related PRs

• feat(gsoc'24): Mobile view Implementation for vue simulator #361 — modifies Extra.vue mobile-related rendering and v-if guards, overlapping with this PR's changes to Extra.vue.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: destructuring props in BooleanTable.vue to remove an unused variable warning. However, the title is only partially aligned with the full changeset, which includes cosmetic refactorings and conditional rendering improvements across multiple other files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/components/DialogBox/BooleanTable.vue`:
- Around line 19-22: Destructuring props directly from defineProps makes
tableHeader and tableBody non-reactive; update the props handling in the
component so the values remain reactive by using toRefs on the object returned
from defineProps (keep the defineProps call but wrap its result with toRefs and
use the toRef-ed symbols tableHeader and tableBody in the template and v-for
loops); ensure any existing references to tableHeader/tableBody in methods or
computed properties use the reactive refs instead of plain values.

🧹 Nitpick comments (1)

src/components/Extra.vue (1)

39-40: Prefer guaranteed-unique keys if messages can repeat.

Using the message text as :key can collide when duplicates exist. Consider adding an index or stable id to keep keys unique.

🧩 Example tweak for uniqueness

-<div v-for="mes in useState().successMessages" :key="mes" class='alert alert-success' role='alert'> {{ mes }}</div>
-<div v-for="error in useState().errorMessages" :key="error" class='alert alert-danger' role='alert'> {{ error }}</div>
+<div v-for="(mes, idx) in useState().successMessages" :key="`success-${idx}-${mes}`" class='alert alert-success' role='alert'> {{ mes }}</div>
+<div v-for="(error, idx) in useState().errorMessages" :key="`error-${idx}-${error}`" class='alert alert-danger' role='alert'> {{ error }}</div>

[s1dhu98]

@Nihal4777 please review the PR and merge it if possible

[Nihal4777]

Hi @s1dhu98, thanks for taking the time to create this PR.
We’re unable to review it because it doesn’t follow our PR template and has no issue linked.
Please update this and your other PRs to align with the template.