You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is a single class with a main method calling static methods. While the code is currently small, this is completely fine and usable, but for future use cases we want to remove these static methods. Consider splitting some of the methods off into a class and create an object of it in the main class to run the methods. In its current state, doing this would create a "fake" object oriented design due to the fact there is only one object running all the code. We are more looking to set a precedent for future changes.
The text was updated successfully, but these errors were encountered:
Currently there is a single class with a main method calling static methods. While the code is currently small, this is completely fine and usable, but for future use cases we want to remove these static methods. Consider splitting some of the methods off into a class and create an object of it in the main class to run the methods. In its current state, doing this would create a "fake" object oriented design due to the fact there is only one object running all the code. We are more looking to set a precedent for future changes.
The text was updated successfully, but these errors were encountered: