[FIX]: Dead Code (Unused Constants)

[prajjwalkumar17]

Summary
Constants are imported but never used, leading to dead code.

Type
cleanup

Context
Unused constants increase maintenance burden. Removing them keeps the codebase clean.

Starter tasks

1. Identify constants flagged as dead code.
2. Remove or annotate with #[allow(dead_code)] if intentional.

Implementation hints

• Run cargo clippy -- -W dead_code.
• If this runs fine proceed with normal cargo clippy command, and do fuzzy search for dead code.

Acceptance criteria

• No unused constants remain.
• No dead_code warnings remain.

Clippy Command

cargo clippy -- -W dead_code

---

Contribution Guidelines:

• Fork the repository and create a new branch for your work.
• Ensure the code follows Rust best practices and coding standards.
• Run cargo clippy and cargo fmt before submitting.
• Add unit tests if functionality changes.
• Keep commits small and meaningful.

Resources:

• Rust Clippy Book
• Rust API Guidelines

Submission Process:

• Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
• Once assigned, submit a pull request (PR).
• Maintainers will review and provide feedback, if any.
• Maintainers can unassign issues due to inactivity, read more here.
• For this issue, please submit a PR on @juspay/deicision-engine repo, and link it to the issue.

Mentor contact
@prajjwalkumar17 @Sarthak1799 @jagan-jaya @GauravRawat369

Pre-flight

• I read the Contributing Guide and setup
• I searched existing issues and PRs

Refer here for Terms and conditions for the contest.

If you have any questions or need help getting started, feel free to ask in the comments!

[Wolfy7]

If you want, you can assign the issue to me, then I will take care of it during the "hacktoberfest"

[neerajkumar-n]

If you want, you can assign the issue to me, then I will take care of it during the "hacktoberfest"

@Wolfy7 - I have assigned another issue, please raise the PR and get this approved.

[Wolfy7]

PR #161 already raised (and some others) feel free to review them.

[neerajkumar-n]

PR #161 already raised (and some others) feel free to review them.

I see that, like I said. Please ensure that you close one PR and come to another one.

[Wolfy7]

Sorry, I don't get it. Why and which PR should I close?

Is something wrong with the PR(s)?