Skip to content

Checklist for permissions/rest refactoring (use specific branch!) #406

@robinharms

Description

@robinharms

Use branch: refactoring/rest_and_perms
(Do something similar in frontend so we can test properly)

Finished in backend, ok to work with:

  • When deleting a room, warn if there are speakers that will be removed. Remove the 'force'-stuff.
  • handle-speaker is now a separate endpoint for handling speaker list related actions that require less permissions than just handle. Make sure to update URLs!
  • Fetching rooms via rest requires meeting as argument. (Probably has no effect on frontend, but do check!)
  • Make sure AutomaticAccess policy work with join the way it's expected to work.
  • Several rest list endpoints may return 400 since a filter is required.
  • Check editing reaction buttons. Should work the same way as before, but some items were missing in the serializer before, if they were used with bogus data something might not work.
  • Verify that org managers can join meetings
  • Move from API organisations to organisation (no list)
  • Move contact info from socket messages to rest API

Metadata

Metadata

Assignees

No one assigned

    Labels

    API changesIssue that requires updates in both frontend and backend

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions