Fix cargo:check script pointing to wrong directory

[Nakshatra480]

Fixes #1088

The cargo:check script was trying to run in the backend/ directory, but that's where the Python code lives. The Rust code is actually in frontend/src-tauri/, so the script was failing with a "manifest not found" error.

Changed the script to point to the correct location. Tested it and it works now.

Summary by CodeRabbit

• Chores
  • Updated the build verification process to run from the frontend source directory. This change realigns the development workflow with the project structure, improving consistency and reliability across the build system while enhancing overall development efficiency.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The cargo:check npm script in package.json was corrected to target the frontend/src-tauri directory instead of the backend directory, aligning with the actual location of the Rust Cargo.toml manifest file.

Changes

Cohort / File(s)	Summary
npm Script Fix package.json	Updated cargo:check script path from backend to frontend/src-tauri to reference the correct Cargo.toml location

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Ah, the path was lost, in backend's deep hole,
But Rust lives upstairs, in src-tauri's abode!
A hop to the right, a script now complete,
Cargo checks smoothly—victory sweet! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: fixing the cargo:check script to point to the correct directory instead of the wrong one.
Linked Issues check	✅ Passed	The changes directly address issue #1088 by updating the cargo:check script in package.json to run in frontend/src-tauri instead of backend, resolving the manifest not found error.
Out of Scope Changes check	✅ Passed	The pull request contains only the necessary change to fix the cargo:check script path and does not introduce any unrelated or out-of-scope modifications.
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.}

---

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.}

[Nakshatra480]

@Pranav0-0Aggarwal @rahulharpal1603 pls review this PR and give me the feedback if anything comes up thankyou

[Nakshatra480]

Pls tell me what is wrong in this PR that it was closed without any comment.
Thank You