[FEATURE] Implement Prettier for automated code formatting

[rohitkumarnaidu]

Feature description

Integrate Prettier into the project for automated code formatting.

Problem it solves

When multiple contributors touch the codebase, inconsistent styling inevitably creeps in, leading to messy diffs and tedious formatting discussions during code reviews.

Proposed solution

I'd love to introduce Prettier to enforce a strict, unified code style automatically. This lets reviewers focus on actual logic rather than syntax. If you agree, please assign this issue to me and add the ELUSOC label so I can get a PR going!

Alternatives considered

We could use standard ESLint without Prettier, but Prettier is the gold standard for pure formatting automation.

Additional context

N/A

[github-actions]

👋 Hello @rohitkumarnaidu!

Thank you for opening this issue on VishwaGuru.

Issue Details:

• Title: [FEATURE] Implement Prettier for automated code formatting
• Number: [FEATURE] Implement Prettier for automated code formatting #944

Next Steps:

1. A maintainer will review your issue
2. The issue may be labeled for categorization
3. Additional information might be requested
4. Once triaged, work can begin!

Tips for a great issue:

• Provide clear steps to reproduce (if it's a bug)
• Include expected vs actual behavior
• Add screenshots or logs if relevant
• Mention your environment details (OS, browser, versions, etc.)

We appreciate your contribution to making VishwaGuru better! 🚀

[rohitkumarnaidu]

Hi @maintainers,

I've outlined my proposed approach for this feature below. My goal is to ensure the implementation aligns perfectly with industry best practices for automated code styling.

Proposed Implementation Plan

• Define Prettier Rules: I will create a .prettierrc file containing standard styling rules (e.g., tab width, single vs double quotes) agreed upon by the community.
• Exclude Build Artifacts: I will add a .prettierignore file so that build directories, logs, and artifacts are not unnecessarily scanned.
• Add Formatting Scripts: I will add standard formatting commands to the package.json to allow developers to format the entire codebase locally with a single command.

Next Steps

If this implementation strategy looks good to the team, I am ready to start working on the Pull Request immediately.

Could you please assign this issue to me and apply the ELUSOC label so I can begin? Thank you!