Backend Tournaments

[sonerkuyar]

Add Tournament and PGN Fetching Endpoints

Description

This PR introduces three new endpoints to enhance the chess tournament features of the application. These endpoints allow fetching tournament details, round-specific information, and PGN (Portable Game Notation) data for games in a specific round. The functionality integrates with the Lichess Broadcast API to retrieve real-time chess tournament data.

Endpoints

1. Get Current Tournaments

• Path: tournaments/
• Function: get_current_tournaments
• Description:
  • Fetches the list of currently ongoing tournaments.
  • Provides essential metadata such as tournament name, description, start and end times, and tier.
  • Utilizes the Lichess API to fetch the live tournament details.

---

2. Get Tournament Round Details

• Path: tournaments/<str:tournamentSlug>/<str:roundSlug>/<str:roundId>/
• Function: get_tournament_round
• Description:
  • Fetches detailed information about a specific tournament round.
  • Includes metadata such as round ID, round name, participating players, and live URLs for games.
  • Maps games using player names and integrates group or tournament-level details.

---

3. Get PGNs for a Tournament Round

• Path: tournament/round/<str:roundId>/pgn/
• Function: get_tournament_round_pgn
• Description:
  • Fetches the PGN representation of all games in a specific tournament round.
  • Maps PGNs to human-readable keys in the format: WhitePlayer - BlackPlayer.
  • Captures headers and moves from the Lichess PGN API for detailed game reconstruction.

Testing

• Ensured PGN parsing is accurate and includes all headers and moves.
• Verified API responses for valid and invalid inputs (e.g., missing round IDs or invalid tournament slugs).
• Tested integration with Lichess API under various conditions (e.g., no ongoing tournaments).

[yusufaygun]

Reviewed the PR, the implementation looks solid with well-documented endpoints and thorough testing. However, I noticed that the PR is opened against the main branch. Was this intentional, or should it be directed to the backend branch instead? If you can confirm the target branch, than it can be merged everything looks good.

[sonerkuyar]

Reviewed the PR, the implementation looks solid with well-documented endpoints and thorough testing. However, I noticed that the PR is opened against the main branch. Was this intentional, or should it be directed to the backend branch instead? If you can confirm the target branch, than it can be merged everything looks good.

It's my mistake. Fixed now!

[yusufaygun]

OK, thanks. Now I am merging.