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

fix(conversations): Remove call-permissions #13086

Merged
merged 3 commits into from
Aug 22, 2024

Conversation

nickvergessen
Copy link
Member

☑️ Resolves

The permission only existed on API level and it's too complicated
to figure out a good UX for it. So the functionality to change it
are removed here. It's still kept in the database and response to
avoid breakage of existing clients

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@nickvergessen nickvergessen added this to the 🖤 Next Major (31) milestone Aug 22, 2024
@nickvergessen nickvergessen requested a review from danxuliu August 22, 2024 10:01
@nickvergessen nickvergessen self-assigned this Aug 22, 2024
@nickvergessen nickvergessen changed the title Bugfix/13012/remove call permissions fix(conversations): Remove call-permissions Aug 22, 2024
Copy link
Member

@danxuliu danxuliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

forcePermissions parameter in joinCall should be deprecated, as it is used to set the now deprecated call permissions.

Same for the whole setAllAttendeesPermissions endpoint (which it is in the docs, although it would be good to mark it too in the code documentation so it is picked by OpenAPI).

@nickvergessen
Copy link
Member Author

forcePermissions parameter in joinCall

It never made it to the normal docs :D So I will remove it, but not deprecate it (as additional send parameters don't break anyway)

Copy link
Member

@danxuliu danxuliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good 👍

The permission only existed on API level and it's too complicated
to figure out a good UX for it. So the functionality to change it
are removed here. It's still kept in the database and response to
avoid breakage of existing clients

Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen nickvergessen force-pushed the bugfix/13012/remove-call-permissions branch from b67edf4 to 6f3da72 Compare August 22, 2024 15:16
Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen
Copy link
Member Author

/backport to stable30

@nickvergessen nickvergessen merged commit cb6da3c into main Aug 22, 2024
145 checks passed
@nickvergessen nickvergessen deleted the bugfix/13012/remove-call-permissions branch August 22, 2024 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug feature: api 🛠️ OCS API for conversations, chats and participants feature: conversations 👥
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove call permissions
2 participants