refactor: remove jQuery & DOM logic from CombinationalAnalysis

[blazethunderstorm]

Fixes #433

Describe the changes you have made in this PR -

removed jQuery & DOM logic from CombinationalAnalysis

Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Summary by CodeRabbit

• Refactor
  • Improved internal handling of table display in dialog boxes for better performance and compatibility. No changes to visible features or user interactions.

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	fbb0c8f
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/684d928309b10500081d129e
😎 Deploy Preview	https://deploy-preview-581--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 32 (🔴 down 15 from production) Accessibility: 72 (no change from production) Best Practices: 92 (no change from production) SEO: 80 (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]

Walkthrough

The update migrates the last remaining jQuery-based DOM manipulation in the printBooleanTable function of CombinationalAnalysis.vue to a Vue 3 ref-based approach, fully aligning DOM access with Vue's reactive system. No other logic or control flow changes are introduced.

Changes

File(s)	Change Summary
src/components/DialogBox/CombinationalAnalysis.vue	Replaced jQuery DOM access in printBooleanTable with Vue ref-based access; added messageBoxRef and updated template to use the ref.

Assessment against linked issues

Objective	Addressed	Explanation
Remove remaining jQuery and DOM manipulations, migrating to Vue's reactives (#433)	✅
Move DOM manipulation logic to respective Vue components and use Vue's reactivity (#433)	✅

Suggested reviewers

• Arnabdaz

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-07T19_11_42_098Z-debug-0.log

---

📜 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 f64c366 and ac53dd2.

📒 Files selected for processing (1)

• src/components/DialogBox/CombinationalAnalysis.vue (4 hunks)

🔇 Additional comments (3)

src/components/DialogBox/CombinationalAnalysis.vue (3)

16-16: Correctly implemented template ref for component access.

The addition of ref="messageBoxRef" properly establishes a reference to the messageBox component, enabling access to its DOM elements without jQuery.

---

34-34: Properly declared Vue ref for component instance.

The reactive reference is correctly declared and will hold the messageBox component instance for DOM access.

---

292-299: Successfully migrated from jQuery to Vue 3 ref-based DOM access.

The implementation correctly replaces $('.messageBox .v-card-text')[0].innerHTML with a Vue ref-based approach. The code includes proper null checks and maintains the same functionality while eliminating the jQuery dependency.

The use of $el to access the component's root DOM element is acceptable here since you need to query within a child component's DOM structure.

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[blazethunderstorm]

@niladrix719 @Arnabdaz pls review the pr , thanks

[Arnabdaz]

@blazethunderstorm can you please also include screen shots and videos and bit better pr description for all your prs. It makes review process easier for the maintainers.

[blazethunderstorm]

@Arnabdaz alright would do it