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]: Operations filtering #63

Open
TylerBloom opened this issue Mar 3, 2023 · 0 comments
Open

[Dev]: Operations filtering #63

TylerBloom opened this issue Mar 3, 2023 · 0 comments
Labels
requirement A requirement for the next major release SquireCore Affects the SquireCore server todo Will be resolved but work hasn't started
Milestone
Server v1.0

Comments

@TylerBloom
Copy link
Member

Unmet Need:

When a user submits a sync request for a tournament, we must verify that the changes that they are submitting for that tournament are allowed to be submitted by them. In other words, players can't submit operations for other players, judges can't submit admin operations, etc. However, if they submit a known operation, they are ok. So, this check should happen after the tournament manager creates the sync processor but before it is processed.
@TylerBloom TylerBloom added todo Will be resolved but work hasn't started SquireCore Affects the SquireCore server requirement A requirement for the next major release labels Mar 3, 2023
@TylerBloom TylerBloom added this to the Server v1.0 milestone Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
requirement A requirement for the next major release SquireCore Affects the SquireCore server todo Will be resolved but work hasn't started
Projects
Squire Tournament Services
Status: No status
Milestone
Server v1.0
Development

No branches or pull requests
1 participant
@TylerBloom