-
Notifications
You must be signed in to change notification settings - Fork 11k
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
base: develop
Are you sure you want to change the base?
Conversation
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
🦋 Changeset detectedLatest commit: 4dc74fd The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
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 ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ 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
Flags with carried forward coverage won't be shown. Click here to find out more. |
Shouldn't this be a Edit: or is it a fix to be able to ship it on patch releases for older versions? |
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 |
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 thesettings
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