Conversation
… limit value is clamped to a maximum of 200 records when the number is bigger (e.g. 999)
…ails as user with ADMIN role
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
| } | ||
|
|
||
| const { userId } = ownership; | ||
| const { userId, event: existingEventOwnership } = ownership; |
There was a problem hiding this comment.
We are not able to track who edited the event as the last one when admin can update it as well.
Only the timestamp of the change is stored without a relation to the author.
We could extend the event table and add columns authorIdCreated and authorIdEdited instead of just authodId.
There was a problem hiding this comment.
I think you've overcomplicated things—wouldn't it be enough to just remove the authorId from the UPDATE statement?
There was a problem hiding this comment.
Maybe, when you add more roles that will enable e.g. sharing event for the users from the same club, it could be useful.
But just removing authorId makes sense and we can extend it later.
There was a problem hiding this comment.
Add competitor search.
It is possible to prolink user name on the event detail tab with the users table in admin zone?
2 participants
Summary
Added pagination to the admin zone and fixed issue with updating original author
Checklist
CLA.mdin therepository root.