Refactor Module-Level Constants to Enums and Classes

[ShearStress021]

** The current codebase utilizes module-level constants for defining various settings, configurations, and related values. While this approach is straightforward, it can lead to issues with organization, readability, and type safety as the project grows. **

[github-actions]

Thank you for creating this issue! 🎉 @SUGAM-ARORA @Ojas-Arora will look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTE.md for guidelines on contributing to this project.

[Ojas-Arora]

@ShearStress021 Tell the solution that you will provide for this.

[ShearStress021]

i would cluster related constants together with either enum, class or namedtuples considering the relationship and datatype of the constants

[Ojas-Arora]

@ShearStress021 Ok, Issue assigned to you.

[Ojas-Arora]

@ShearStress021 What's the progress on this issue?

[ShearStress021]

I’m going to work on the issue this weekend. I got a little busy over the past few days. can please also give the explanation on how to play the game.

[Ojas-Arora]

@ShearStress021 U just neeed to run the main.py and make sure all the requirements libraries are installed.

[ShearStress021]

the game is running but i think on the help icon instructions on how to play the game are needed

[Ojas-Arora]

The given Instructions are sufficient to know how to play game if u have some more instructions that can be added u can add so.

[github-actions]

Hello @ShearStress021! 🎉

Your issue #1 - Refactor Module-Level Constants to Enums and Classes has been successfully closed.

We appreciate your valuable contribution and your help in improving the project. If you have any more ideas, questions, or issues, feel free to open a new issue or join the discussion in our community forum.

Stay awesome! 😊