Fields Query Parameters not working on livechat rooms list endpoint
Description:
Fields Query Parameters not working on livechat rooms list endpoint
Steps to reproduce:
- Send request with query or fields parameter on endpoint '/api/v1/livechat/rooms'
- Returned all rooms without apply query or fields
Expected behavior:
Rooms can be filtered by fields
Actual behavior:

Server Setup Information:
- Version of Rocket.Chat Server: 3.14.0
- Operating System: Windows 11
- Number of Running Instances: 1
Hi!
I have checked on latest code, and looks that query parameter is still not supported: (files have been changing places due to some coding refactoring for monorepo)
https://github.com/RocketChat/Rocket.Chat/blob/f0c37c5a8c904181577b80d239255284ac6a1280/apps/meteor/app/livechat/imports/server/rest/rooms.js#L26
Also, tried to look for other endpoint but it filters by t: "c".
I will mark as bug and raise it with our team.
Thanks for pointing out.
This is the documentation of this API, for reference: https://developer.rocket.chat/reference/api/rest-api/endpoints/omnichannel/omnichannel-endpoints/rooms/livechat-rooms-list
@dudanogueira Could I attempt to fix this issue? And if so, would you mind assigning it to me?
I want to work on the issue. Could you please assign it to me.
@ykabusalah @Shofiya2003 feel free to work on this. Please join our #contributors channel and leave me a ping (@debdut.chakraborty). You can ask me any related questions there.
@debdutdeb I was working on the issue. I followed all the steps in the documentation to setup rocket chat locally but when I run yarn build I get this error 'command (packages/ui-contexts) yarn run build exited (129)' . Could you please help me?
@debdutdeb I tried pulling the changes but there are some changes in the folder that I did not make. I tried stashing and reverting them but there is an error. What should I do? error: lstat("apps/meteor/.storybook/.eslintrc.js"): Function not implemented
fatal: Unable to process path apps/meteor/.storybook/.eslintrc.js
Cannot save the current worktree state
This it the error which I get after staging and stashing the commits Should I do the cloning process again?
Hi, is this issue still open? Can I start working on it? @debdutdeb
I have explored the codebase related to this issue, currently, I guess instead of query support, custom fields are given to perform any search for custom fields. Am I correct?
Hi, @debdutdeb is this issue still open I want to work on this issue. Can you please assign this to me?
Hey @debdutdeb @dudanogueira is this issue still relevant I mean has it been patched or by-passed in previous version's
Has this issue not been fixed by this PR? May I know why it was closed @dudanogueira ?
Hi, I’m interested in working on this issue. Could you assign it to me, or let me know if it’s already being worked on?@dudanogueira
I would love to pick this up!
Can i get assigned this issue?
Hello! I’m new to open source but eager to learn and contribute. I’d like to work on this issue.
Hello! I'm new to open source and i would like to work on this issue
Hello i am new to open source and i would like to work on this issue
Hi, I'm new to open source and I'd like to work on this issue.
Hello i am new to open source and i would like to work on this issue
Hi 👋
I’m a beginner contributor and would like to work on this issue.
Is it still valid, and can you please assign it to me or guide me where to start?