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

Add state management to tournaments #690

Open
evroon opened this issue May 4, 2024 · 1 comment
Open

Add state management to tournaments #690

evroon opened this issue May 4, 2024 · 1 comment
Labels
enhancement New feature or request Stale

Comments

@evroon
Copy link
Owner

evroon commented May 4, 2024

spinoff from: #650

  1. Tournament States: Define states such as [Draft], [Running], and [Archived] to manage the tournament lifecycle more effectively. In the [Draft] state, all data can be modified without entering match results. Once in the [Running] state, only match results should be updatable. Finally, the [Archived] state would freeze all data, allowing only queries.

We should implement archiving tournaments and making them read-only.

In running state, more should be able to be updated than just match results IMO. Bracket should be flexible enough (and already is) to handle changes to team setups or changing team names etc. during tournaments, which is an important feature that other tools don't have.

The draft state is IMO just the same as the regular state, except that it isn't visible publicly (for which option there is already support), so I don't think we need that.

@evroon evroon added the enhancement New feature or request label May 4, 2024
Copy link
Contributor

github-actions bot commented Jul 4, 2024

This issue is stale because it has been open for 60 days with no activity. What is the action to take here?

@github-actions github-actions bot added the Stale label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

1 participant