Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor Game Score Functions #84

Open
nery-lara opened this issue Dec 6, 2017 · 1 comment
Open

Refactor Game Score Functions #84

nery-lara opened this issue Dec 6, 2017 · 1 comment

Comments

@nery-lara
Copy link
Contributor

There is a lot of duplicate code for keeping track of the high score and score of the game. These functions are found in the classes for every level. Factor them out so that they are only declared once in the entire project and have the methods just be called when needed.

@joelbagan
Copy link
Contributor

Renaming to "Refactor Game Score Functions"

Consider creating a helper class which each level/difficulty has an instance of, which handles the score.

F17 OK 100pts

@joelbagan joelbagan changed the title Abstract out functions for game scores Refactor Game Score Functions Dec 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants