Remove redundant code

[RipulHandoo]

Proposed changes

This pull request addresses the issue [ https://github.com//issues/4206 ], which was about removing inefficient code that was causing redundant conditions in the codebase.

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

N/A

Special notes for your reviewer:

N/A

[Saranya-jena]

Build checks are failing, can you PTAL @RipulHandoo

[RipulHandoo]

@Saranya-jena I raised a new PR. This time all the checks have passed.

[Saranya-jena]

You have updated this branch right? @RipulHandoo

[RipulHandoo]

@Saranya-jena should I raise PR again.
Yes

[amityt]

Hi @RipulHandoo , thanks for the contribution! There are some merge conflicts, can you please update your PR!

[RipulHandoo]

Hi @RipulHandoo , thanks for the contribution! There are some merge conflicts, can you please update your PR!

@amityt I've solved the conflicts.
PTAL!

[hrishavjha]

Changes looks good to me 🚀

[arkajyotiMukherjee]

Thanks for your contribution to the litmus repo @RipulHandoo 🚀