Closed ErwanTLG closed 3 years ago
Let's say I have the tournament id or url stored in my database. The only way to do an api call on this tournament is to first get the tournament, then call the api, like this:
Tournament tournament = await challongeClient.GetTournamentByUrlAsync(tournamentUrl); await challongeClient.StartTournamentAsync(tournament);
The idea is to add methods overloads which would allow the client to directly pass the url as the parameter for the api call, like this:
await challongeClient.StartTournamentAsync(tournamentUrl);
This would reduce the number of lines (improving code clarity), and reduces the number of api calls (improving performance).
This was originally the intended usage for such a scenario, but you're right, it's cumbersome and inefficient. Please proceed.
Let's say I have the tournament id or url stored in my database. The only way to do an api call on this tournament is to first get the tournament, then call the api, like this:
The idea is to add methods overloads which would allow the client to directly pass the url as the parameter for the api call, like this:
This would reduce the number of lines (improving code clarity), and reduces the number of api calls (improving performance).