Skip to content

Clapper result personalisation #17

Description

@rmil

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions