-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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: Remove users upsert behavior #31822
Conversation
🦋 Changeset detectedLatest commit: 00cea1e The changes in this PR will be included in the next version bump. This PR includes changesets to release 31 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 #31822 +/- ##
========================================
Coverage 54.48% 54.49%
========================================
Files 2275 2275
Lines 50138 50141 +3
Branches 10226 10226
========================================
+ Hits 27319 27324 +5
+ Misses 20338 20336 -2
Partials 2481 2481
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest creating different PRs for each of the purposes, one fix
for each fix we are doing here ("accept the settings
field" and another one for "accept the language field").
Then we should create a PR for the deprecation method (insertOrUpdateUser
), and finally another PR for the "removal of upsert behavior".
Thanks for the suggestion, @MarcosSpessatto |
Proposed changes (including videos or screenshots)
users.update
endpoint (by making_id
field required);insertOrUpdateUser
Meteor method;users.update
andusers.create
params check to accept thesettings
field, which was already expected by them internally (this allow users to set their language preference, for example);users.update
params check to accept thelanguage
field, which was already expected by its internal flow.Issue(s)
Steps to test or reproduce
Further comments
CORE-79