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.
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
Add optional win condition feature #34
Add optional win condition feature #34
Changes from 1 commit
3d7d4f0
00a5794
d2a5c9b
991b485
512e48f
63c50f8
59c42ca
59d09ac
96c073d
d8de90f
c2a7253
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will not actually apply the action properly! You need to move this case up to where
case 'GameEnd':
is to make sure it callsapplyGameOverActionResponse
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see. Just to make sure we're on the same page though, this is for the consumers of
applyActionResponse()
, right? Would it be possible for that consumer to callapplyGameOverActionResponse()
instead? Or maybe it's impossible to do so in some cases?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this is funky since the function name/module name no longer makes sense now. Maybe we should rename this to
getMatchingTeam
since it gives us the team matching the ActionResponse?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just my opinion, but I see
processRewards()
is the sole consumer of thisgetWinningTeam()
function in the entire codebase, and it checks if the return value is'draw'
(i.e.,winningTeam !== 'draw'
).It just occurred to me that it might be a little awkward to have
matchingTeam !== 'draw'
? In theprocessRewards()
perspective, I think it makes more sense to call itwinningTeam
indeed, since the winner takes the rewards?Maybe we could wait until there are other use cases that calling
getWinningTeam()
wouldn't make sense at all?Or maybe we could bring
getWinningTeam()
intoprocessRewards.tsx
as a local function and worry about other use cases later?