feat: Return departmentsAllowedToForward property in livechat/config endpoint

[matheusbsilva137]

Proposed changes (including videos or screenshots)

• Add departmentsAllowedToForward property to departments returned by the livechat/config endpoint (this is a requirement for a client improvement described in CORE-410)

Issue(s)

Steps to test or reproduce

Further comments

CORE-652

[dionisio-bot]

Looks like this PR is not ready to merge, because of the following issues:

• This PR is targeting the wrong base branch. It should target 7.3.0, but it targets 7.2.0

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

[changeset-bot]

🦋 Changeset detected

Latest commit: a215a9d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 35 packages

Name	Type
@rocket.chat/meteor	Minor
@rocket.chat/livechat	Minor
@rocket.chat/model-typings	Minor
@rocket.chat/apps	Patch
@rocket.chat/models	Patch
@rocket.chat/account-service	Patch
@rocket.chat/authorization-service	Patch
@rocket.chat/ddp-streamer	Patch
@rocket.chat/omnichannel-transcript	Patch
@rocket.chat/presence-service	Patch
@rocket.chat/queue-worker	Patch
@rocket.chat/stream-hub-service	Patch
@rocket.chat/omnichannel-services	Patch
rocketchat-services	Patch
@rocket.chat/core-services	Patch
@rocket.chat/cron	Patch
@rocket.chat/instance-status	Patch
@rocket.chat/presence	Patch
@rocket.chat/network-broker	Patch
@rocket.chat/core-typings	Minor
@rocket.chat/rest-typings	Minor
@rocket.chat/uikit-playground	Patch
@rocket.chat/api-client	Patch
@rocket.chat/ddp-client	Patch
@rocket.chat/freeswitch	Patch
@rocket.chat/fuselage-ui-kit	Major
@rocket.chat/gazzodown	Major
@rocket.chat/ui-contexts	Major
@rocket.chat/license	Patch
@rocket.chat/pdf-worker	Patch
@rocket.chat/ui-avatar	Major
@rocket.chat/ui-client	Major
@rocket.chat/ui-video-conf	Major
@rocket.chat/ui-voip	Major
@rocket.chat/web-ui-registration	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 60.23%. Comparing base (86a21b5) to head (a215a9d).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #33060      +/-   ##
===========================================
+ Coverage    59.27%   60.23%   +0.95%     
===========================================
  Files         2820     2684     -136     
  Lines        67843    66163    -1680     
  Branches     15075    14634     -441     
===========================================
- Hits         40216    39855     -361     
+ Misses       24810    23513    -1297     
+ Partials      2817     2795      -22     

Flag	Coverage Δ
unit	75.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[github-actions]

PR Preview Action v1.4.8
🚀 Deployed preview to https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-33060/
on branch gh-pages at 2024-12-26 12:02 UTC

[MartinSchoeler]

Is it possible to add some UI e2e tests? I know we didn't change any client files, but there are some behavior changes on the UI, I think we can add one to this file https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/tests/e2e/omnichannel/omnichannel-livechat-department.spec.ts or even a livechat API test to check if the widget api is respecting the fowarding limits implemented here

[tapiarafael]

Is it possible to add some UI e2e tests? I know we didn't change any client files, but there are some behavior changes on the UI, I think we can add one to this file develop/apps/meteor/tests/e2e/omnichannel/omnichannel-livechat-department.spec.ts or even a livechat API test to check if the widget api is respecting the fowarding limits implemented here

I was looking at the code/task, and I don't think that there are any changes in the UI, the PR only returns a new field so the frontend can use it to filter the departments correctly, no?

Fair enough, dismissing this review