Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clapper result personalisation #17

Open
2 tasks
rmil opened this issue Jan 12, 2022 · 0 comments
Open
2 tasks

Clapper result personalisation #17

rmil opened this issue Jan 12, 2022 · 0 comments

Comments

@rmil
Copy link
Member

rmil commented Jan 12, 2022

Currently clapper endpoints are designed a bit too similarily to the database. This is fine for an event admin, but we need to add some new one's which cover a user's perspective better.

Endpoint areas to need work on:

  • The view endpoints need to updated to include information if the user is signed up or is an admin of an event.
  • Event endpoints don't include what level of access a user has to the selected event. Will need to check if a user is in a admin position or has a permission changing their access level.

Keeping the existing endpoints is a must since they would be useful for other views.

There are also likely to be more endpoints which need this personalisation, if any are discovered popping them as a comment on this issue would be ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant