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

quick and dirty fix to issue #45 #52

Merged

Conversation

official-sounding
Copy link
Contributor

fixes Issue #45 by adding EXP-* codes to the FO_EXP list of penalties, with a subset of penalties that are expellable.

Since this is an officials best practice/paperwork requirement, I am adding this as a stopgap while I work on converting the penalty code definition to something based on a runtime-loaded file and less copy-and-paste terrible, like an "can expel" flag on a penalty definition.

since this is an officials best practice/paperwork requirement, I am adding this as a stopgap while I work on converting the penalty code definition to something based on a runtime-loaded file and less copy-and-paste terrible (like an "is expellable" flag on a penalty definition).
updateMap.put("PenaltyCode.FO_EXP(EXP-D)", "Expulsion-Direction");
updateMap.put("PenaltyCode.FO_EXP(EXP-P)", "Expulsion-Illegal Position");
updateMap.put("PenaltyCode.FO_EXP(EXP-N)", "Expulsion-Interference");
updateMap.put("PenaltyCode.FO_EXP(EXP-G)", "Expulsion-Misconduct");
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we add unknown too? It seems unlikely to come up, but it's possible.

Copy link
Contributor

@JeneralPain JeneralPain May 31, 2018

Choose a reason for hiding this comment

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

I would add unknown for the sake of it

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, it's worth it for consistency I think.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can you add it to your pull so when I merge or Jared does we can capture it?

Copy link
Contributor

Choose a reason for hiding this comment

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

I can create a quick PR after you merge for the sake of simplicity. My PR is big enough as-is.

Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, better idea. #62 contains both @official-sounding's commit and this change so you can merge or rebase that one, and close this one.

Copy link
Contributor

@JeneralPain JeneralPain left a comment

Choose a reason for hiding this comment

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

Approve to Merge pending Jared.

@JeneralPain JeneralPain removed the bug label May 31, 2018
@jaredquinn jaredquinn merged commit d78bb07 into rollerderby:dev Jun 6, 2018
jaredquinn added a commit that referenced this pull request Jun 6, 2018
…and-unknown

PR #52 with unknown expulsion code added
@official-sounding official-sounding deleted the bugfix/exp-penalty-codes-qd branch July 8, 2018 22:10
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

Successfully merging this pull request may close these issues.

4 participants