add and edit matches manually

[varCepheid]

Admins and super-admins can create new matches for an event manually and edit existing matches. The editable fields are name, date & time, team list, and score.

[varCepheid]

@calebeby When I try to test the match-creator form in the deploy preview, it throws a red Alert popup, but it doesn't tell me what the problem is. Can you look through the code and tell me if there's anything that should cause a problem?

[varCepheid]

The same error occurs when saving the match-editor form.

[calebeby]

@varCepheid When I look in devtools it shows me that the PATCH request did not go through; the server returned a 405 Method Not Allowed:

Based on the API Docs for the backend, it looks like the server does not support updating matches, only creating new ones. So we are missing a backend method that you (or someone) will need to send a PR for.

[calebeby]

Looks like there is an undocumented PUT for updating matches. Maybe you can use that instead of PATCH: https://github.com/Pigmice2733/peregrine-backend/blob/develop/internal/server/routes.go#L40C26-L40C26

And the POST method for /events/{eventKey}/matches in the documentation is not implemented. You should be able to use the PUT directly to make a match instead of using the POST.

Maybe it would be good to update the OpenAPI docs in https://github.com/Pigmice2733/peregrine-backend/blob/develop/internal/server/openapi.yaml

Feel free to send a PR!

cc @brendanburkhart

[varCepheid]

The forms are going through fine now. I've fixed all the problems I could find except that when I go into the match editor, it will always display (in the placeholder attribute) the current date-time instead of the match's date-time. It should only do that if it is unable to load the match or the match's time property in the code, but it's weird to me that it wouldn't be able to load that information, since it displays correctly on the match card. Any ideas?

[calebeby]

@varCepheid It is because the match variable is null for a bit while useMatchInfo is fetching the match info. During that time, matchDate gets set to the current time, and then day and time get initialized with those values. You did not write any code to update day and time when matchDate changes (/ is loaded). You could use a useEffect for this?

[varCepheid]

Added the useEffect call and fixed the problem that I mentioned in issue #1536.