Missing `tournament` features

InsaLan / backend-insalan.fr

Backend of the insalan website

MIT License

2 stars 0 forks source link

Missing `tournament` features #31

Open Lymkwi opened 1 year ago

Lymkwi commented 1 year ago

Here are some more advanced features needed for a fully functional tournament module:

[x] Tournaments should store an icon (f35ce3f565140bd29567195081568d0b90bedb94)
[x] Tournaments should store rules (f35ce3f565140bd29567195081568d0b90bedb94)
[ ] Tournaments should store winner teams
[ ] Tournaments should store a tree of matches
[ ] Missing match and tree structures (see the minutes of the Tournament team meeting)
[x] Events should store an icon (ff7fa5ca66c53c1d99c1e629102938c14e2f08e0)

ShiroUsagi-san commented 1 year ago

Shall we add a cancellation_deadline in the model or shall we compute it (in the validator of cancellation endpoint)?

Lugrim commented 1 year ago

Shall we add a cancellation_deadline in the model or shall we compute it (in the validator of cancellation endpoint)?

From experience, we should add it to the model (and maybe compute it to a default on tournament creation, but it should be editable, I was asked to change it in the past, there is no reason it couldn't happen again)

Lymkwi commented 1 year ago

Shall we add a cancellation_deadline in the model or shall we compute it (in the validator of cancellation endpoint)?

From experience, we should add it to the model (and maybe compute it to a default on tournament creation, but it should be editable, I was asked to change it in the past, there is no reason it couldn't happen again)

Will be doable because Django lets you use functions for default values

Lymkwi commented 1 year ago

oops