elliehield / gmsv2 Goto Github PK

A Team requires the following fields:

• Club: Club (see #8)
• League: Enum (start with some dummy leagues)

The team page should be accessible from the teams list on the club page

Enum values such as League or Gender are printed in capital letters on the frontend, which looks a bit funny.

We should find a way to make it look prettier, i.e. have a String property on the Enum and return that value to the frontend?

Accessible from the club view page

Create a new club form and create a reusable form component on the front end with basic styling

• enforce club short name as 3 characters
• mandatory fields (name, short name, address)

endpoints required:

getAllClubs GET /clubs
getClubById GET /clubs/{id}
addClub POST /clubs
deleteClub DELETE /clubs/{id}
editClub PATCH /clubs/{id}

Using agGrid display a list of all clubs with the ability to navigate to individual clubs from their rows

Currently all of our front-end relies on ag-grid. Let's instead depend on a shared grid component :)

run ng serve and whatever the back end test command is, must pass before merging to main

endpoints required:

• getAllPlayers() GET /players
• getAllPlayersForClub() GET /players/{club}
• getAllPlayersForTeam() GET /players/{team}
• getPlayer GET /player/{id}
• addPlayer POST /players
• editPlayer PATCH /players/{id}
• deletePlayer DELETE /players/{id}

a Player should have the following fields:

• Name: string
• Email address: string
• Home address: string
• Team: Team (see #9) (a player should be able to belong to one team only), this should link to the team display page

TODO: decide how to navigate to player page, possible suggestions so far:

• search function on home screen for all player search with filters for club and team
• list of players on team page

Make a "pretty" logo and add it to the home page

Make columns sensible widths (resizable)
Make grid not take up all the space

Options:

1. Use long name with no spaces, e.g. /clubs/amazing-club/.
   1. Player names may not be unique so would need a way around this, e.g. /players/bob-bobson-3/
   2. Names of clubs, teams and players may change, so IDs may change then. On a modification or addition of club/team, the pretty ID could be changed, e.g. /players/alice-maiden/ to /players/alice-married/. The old links would become dead.
2. Use plain numbers, e.g. /clubs/123456/.
   1. We'd need to keep track of which IDs have been used. Currently the DB is in-memory, so the server could keep track of IDs, but the database was more persistent, this would be more complex.
3. Use UUIDs, e.g. /clubs/c09b4643-4632-4ea1-8df4-626aa769344a which would be unique, but do not look pretty.
   1. We wouldn't have the complexity of having to convert between pretty IDs and real IDs.

Use angular CLI to create new project

Implement basic agGrid, add some sample data and unit/e2e tests
blocked by #1

Add basic log in ability

We need an Endpoint to return a list of players associated with a team.

The frontend currently returns ALL players in team.service.ts. The request in this service has to be updated when the endpoint is there.

An individual club needs the following fields:

• Name: string
• id: string (uuid)
• Address: string
• Short name: string (3 chars)
• Teams: Teams Array

endpoints required:

• getAllTeams() GET /teams
• getTeam() GET /teams/{id}
• getAllTeamsForClub() GET /club/teams (can't decide if this should be a clubs endpoint or a teams one - will leave it to whoever picks it up)
• addTeam() POST /teams
• editTeam() PATCH /teams/{id}
• deleteTeam() DELETE /teams/{id}