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: Allow users to fetch the packageValue of settings on /settings endpoint #34864

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

KevLehman
Copy link
Contributor

@KevLehman KevLehman commented Jan 2, 2025

Proposed changes (including videos or screenshots)

Since fields param is deprecated (and it's disabled by default, behind an env var), there was no way to obtain the default value of the settings when using the settings endpoint.

The proposed solution is to use a new boolean flag that allows the requester to fetch the packageValue along with the current value when using the aforementioned endpoint.

Flag is includeDefaults

Issue(s)

https://rocketchat.atlassian.net/browse/CORE-911

Steps to test or reproduce

Further comments

Copy link
Contributor

dionisio-bot bot commented Jan 2, 2025

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

  • This PR is missing the 'stat: QA assured' label
  • 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

Copy link

changeset-bot bot commented Jan 2, 2025

🦋 Changeset detected

Latest commit: 4dc74fd

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

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

Copy link
Contributor

github-actions bot commented Jan 2, 2025

PR Preview Action v1.4.8
🚀 Deployed preview to https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-34864/
on branch gh-pages at 2025-01-03 14:53 UTC

Copy link

codecov bot commented Jan 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.16%. Comparing base (7619988) to head (4dc74fd).
Report is 3 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff            @@
##           develop   #34864   +/-   ##
========================================
  Coverage    59.16%   59.16%           
========================================
  Files         2821     2821           
  Lines        68045    68045           
  Branches     15116    15116           
========================================
  Hits         40261    40261           
  Misses       24959    24959           
  Partials      2825     2825           
Flag Coverage Δ
unit 74.99% <ø> (ø)

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

@KevLehman KevLehman marked this pull request as ready for review January 2, 2025 16:48
@KevLehman KevLehman requested review from a team as code owners January 2, 2025 16:48
MarcosSpessatto
MarcosSpessatto previously approved these changes Jan 2, 2025
@MarcosSpessatto MarcosSpessatto added this to the 7.3.0 milestone Jan 2, 2025
@debdutdeb
Copy link
Member

debdutdeb commented Jan 3, 2025

Shouldn't this be a feat instead? I understand why it could be considered a fix, however it's a new thing that's being added?

Edit: or is it a fix to be able to ship it on patch releases for older versions?

@KevLehman
Copy link
Contributor Author

Well, it's a funny story: this was working, then it stopped working, then this will make it work again. So in theory is a fix... but could be a feat as well (as a new thing is added).

But i'm inclined more to "fix" cause it was working in a way and it stopped working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants