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.

Sign up for GitHub

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

Jump to bottom

[Dev]: Record Result Operation #27

Closed
TylerBloom opened this issue Aug 13, 2022 · 0 comments
Closed

[Dev]: Record Result Operation #27

TylerBloom opened this issue Aug 13, 2022 · 0 comments
Assignees
@TylerBloom
Labels
good first issue Good for newcomers in progess Actively being worked on requirement A requirement for the next major release SquireLib Affects SquireLib
Milestone
SquireLib v1.0

Comments

@TylerBloom
Copy link
Member

Currently, the record result operation never checks if the player is in the match. The operation should have an additional field for the player's id to ensure that the player is in the round.
@TylerBloom TylerBloom added good first issue Good for newcomers todo Will be resolved but work hasn't started SquireLib Affects SquireLib requirement A requirement for the next major release labels Aug 13, 2022
@TylerBloom TylerBloom added this to the SquireLib v1.0 milestone Aug 13, 2022
@TylerBloom TylerBloom mentioned this issue Aug 13, 2022
Closed
@TylerBloom TylerBloom self-assigned this Aug 27, 2022
@TylerBloom TylerBloom added in progess Actively being worked on and removed todo Will be resolved but work hasn't started labels Aug 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TylerBloom TylerBloom

Labels
good first issue Good for newcomers in progess Actively being worked on requirement A requirement for the next major release SquireLib Affects SquireLib
Projects
Squire Tournament Services
Status: Done
Milestone
SquireLib v1.0
Development

No branches or pull requests
1 participant
@TylerBloom