-
Notifications
You must be signed in to change notification settings - Fork 24
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
feat: Channel and Group #kick APIs #39
base: main
Are you sure you want to change the base?
feat: Channel and Group #kick APIs #39
Conversation
Not sure I follow what you mean about the APIs not allowing and Specifically from the And the |
The |
Still happy to accept a PR improving the docs and specs, although another spec or two to test the username/room name options would be nice (and removing the channel/group kick methods). |
@abrom Sorry I was looking at https://developer.rocket.chat/ docs instead of the actual code on GitHub and there is no mention of the user#username param. I will undo the changes made and improve specs as well, just one unrelated question: Why are Thanks! |
No problems! Yeah the rocketchat docs are a little misleading on that front. I had to go hunting through the code base to find the real story 😉 Regarding custom fields, are you referring to https://developer.rocket.chat/reference/api/rest-api/endpoints/core-endpoints/channels-endpoints/setcustomfields ? (and similar for groups of course) If so, it looks like that also supports finding the channel by ID or name (same as But yes, absolutely. PR's welcome! |
Added:
Channel Kick API
Group Kick API
Specs are passing
Rubocop is passing
@abrom Since both API's do not allow
user#username
androom#name
, I'm sending it asnil
onuser_params
androom_params
respectively.