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

make use of new getAllHitpointsDamage command #2319

Merged
merged 1 commit into from
Sep 21, 2015
Merged

Conversation

commy2
Copy link
Contributor

@commy2 commy2 commented Aug 30, 2015

No description provided.

@commy2 commy2 added kind/enhancement Release Notes: **IMPROVED:** kind/cleanup Release Notes: **CHANGED:** labels Aug 30, 2015
@commy2 commy2 self-assigned this Aug 30, 2015
@commy2 commy2 added this to the 3.4.0 milestone Aug 30, 2015
@commy2 commy2 changed the title make use of getHitpointsDamage command make use of new getAllHitpointsDamage command Aug 30, 2015
@@ -215,6 +215,7 @@ PREP(getConfigGunner);
PREP(getConfigCommander);
PREP(getHitPoints);
PREP(getHitPointsWithSelections);
PREP(getSelectionsWithoutHitPoints);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A better name might be getSelections so it would mirror getHitPoints, that automatically implies it's without anything else.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But those are only the selections that don't have any hitpoint assigned, not all damageable selections.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just make them into one function anyways and parameterize it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just make them into one function anyways and parameterize it?

It's a completely different approach as getHitpoints. I personally don't like the overhead that comes with checking optinal parameters when nothing but one line is shared between both functions.

@jonpas jonpas mentioned this pull request Aug 30, 2015
13 tasks
@commy2 commy2 removed kind/enhancement Release Notes: **IMPROVED:** needs review labels Sep 21, 2015
@commy2 commy2 merged commit c3beee8 into master Sep 21, 2015
commy2 added a commit that referenced this pull request Sep 21, 2015
common code cleanup part 10, close #2319
@commy2 commy2 deleted the 323cleanuphitpoints branch September 21, 2015 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Release Notes: **CHANGED:**
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants