refactor: Js to Ts : src/simulator/src/hotkey_binder/view/panel.ui.js

[ThatDeparted2061]

Fixes https://github.com/CircuitVerse/cv-frontend-vue/issues/414

cc @niladrix719

The netlify link generated by netlify bot wont work, since many files are inter-related with JS specifying the format as .js while calling different files within themselves, just checking one file will throw error since the new format is .ts !

Summary by CodeRabbit

• Refactor
  • Migrated hotkey panel UI management functions from JavaScript to TypeScript
  • Improved type safety and maintainability of hotkey configuration interface
  • Enhanced functions for updating, overriding, and submitting hotkey settings
  • Removed outdated hotkey panel UI management functions
  • Introduced new functions for dynamic updates and error handling in hotkey configurations
  • Added functionality to display error messages to users during key configuration updates

[coderabbitai[bot]]

Walkthrough

The pull request involves the deletion of the panel.ui.js file and the addition of the panel.ui.ts file, effectively migrating the hotkey management functionality from JavaScript to TypeScript. The new TypeScript file introduces enhanced functionality, including error handling and improved UI updates, while maintaining the core features related to managing user-defined hotkeys. This transition includes the addition of type annotations for better type safety.

Changes

File	Change Summary
src/simulator/src/hotkey_binder/view/panel.ui.js	Deleted JavaScript file containing hotkey management functions
src/simulator/src/hotkey_binder/view/panel.ui.ts	Added TypeScript equivalent with type annotations and enhanced functionality

Assessment against linked issues

Objective	Addressed	Explanation
Typescript Integration in /simulator/src files [#414]	✅

Poem

🐰 Typescript hops in with grace,
Replacing JS at steady pace
Type annotations take their flight
Bringing code clarity so bright!
A rabbit's leap to cleaner code 🚀

✨ Finishing Touches

• [ ] 📝 Generate Docstrings (Beta)

---

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[bot]]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	54abeda35b4ce75c2bc83692c8d07749111ee52f
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/684d885bc0ace800080eb283
😎 Deploy Preview	https://deploy-preview-429--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 1 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.