Refactor move() into Move() class #55
Open
+112
−48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I refactored the move() method in main.py into a dedicated Move() class in a new file move.py. This organization helps newcomers to understand that not every part in main.py is a part of the bot logic. It separates the handler from the bot logic clearly.
The class uses a structured data format for moves: {str move: {is_safe: bool}} e.g. {"left": {is_safe: False}}
This structure is easily extendable for example by adding a priority key for more advanced move logic.
At least I added a test package which ensures that the class works as expected.