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]: Transition to TournamentManagers #67

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

[Dev]: Transition to TournamentManagers #67

TylerBloom opened this issue Mar 2, 2023 · 0 comments
Assignees
@TheDeveloper101
Labels
good first issue Good for newcomers todo Will be resolved but work hasn't started
Milestone
SquireCore Integr...

Comments

@TylerBloom
Copy link
Member

Unmet Need:

Currently, SquireBot directly manipulates the tournaments. Integration with the SquireCore server will require the use of the TournamentManager defined in the SquireSDK. This is a breaking change as there is no way to convert a tournament into a tournament manager since the manager tracks all operations that are successfully applied to the tournament.
@TylerBloom TylerBloom added good first issue Good for newcomers todo Will be resolved but work hasn't started labels Mar 2, 2023
@TylerBloom TylerBloom added this to the SquireCore Integration milestone Mar 2, 2023
@TylerBloom TylerBloom changed the title [Dev]: Transition to TournamentMangers [Dev]: Transition to TournamentManagers Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheDeveloper101 TheDeveloper101

Labels
good first issue Good for newcomers todo Will be resolved but work hasn't started
Projects
Squire Tournament Services
Status: No status
Milestone
SquireCore Integration
Development

No branches or pull requests
2 participants
@TylerBloom @TheDeveloper101