Players might have their official IFPA name changed from time to time and they currently have a way to update that in our system. You might ask why not just use IFPA player numbers and call it a day, but the reality is that not all players have one. What do you do in those cases? The system currently allows those players to sign up and enter scores, and we would like to make sure that non-IFPA players can still participate.
To make this happen:
- Update player key system to be independent from names
- Update auth and session info
- GET /player/:key/edit route OR maybe have EditableText field on the /profile page.
- POST /player/:key/edit route (probably should be a PUT, but we use all POSTs).
- Alert players on /profile that their name is jacked up. (BONUS: Show link to team, player page, and current match/games).
Alternative (quick and dirty):
- Change the signup logic to overwrite name
- Change player key based on new name
- Move player file to new key
- Update auth and session info
Note that the auth and session parts will need to be updated in either case, and might be one of the trickier things, given how funky the code is. This is the kind of issue that makes me want to just throw away the current model and try to integrate the new backend. But I know that is a gigantic can of worms to the point where it might make more sense to just start a completely new frontend. It could still leverage most of the templates to some extent, but it's not going to happen for season 10.
Players might have their official IFPA name changed from time to time and they currently have a way to update that in our system. You might ask why not just use IFPA player numbers and call it a day, but the reality is that not all players have one. What do you do in those cases? The system currently allows those players to sign up and enter scores, and we would like to make sure that non-IFPA players can still participate.
To make this happen:
Alternative (quick and dirty):
Note that the auth and session parts will need to be updated in either case, and might be one of the trickier things, given how funky the code is. This is the kind of issue that makes me want to just throw away the current model and try to integrate the new backend. But I know that is a gigantic can of worms to the point where it might make more sense to just start a completely new frontend. It could still leverage most of the templates to some extent, but it's not going to happen for season 10.