feat: Audit users.update API endpoint#34494
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: 1e260e4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 36 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 ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #34494 +/- ##
========================================
Coverage 59.73% 59.73%
========================================
Files 2830 2830
Lines 68258 68258
Branches 15130 15130
========================================
Hits 40772 40772
Misses 24877 24877
Partials 2609 2609
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Gabriel Henriques seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
pierre-lehnen-rc
left a comment
There was a problem hiding this comment.
Not a big deal but I'd prefer if extra data like the active here was passed on from outside instead of adding it automatically whenever the function gets called.
As it is, you're assuming that any place that calls saveUser will also call setUserActiveStatus.
Co-authored-by: Pierre Lehnen <55164754+pierre-lehnen-rc@users.noreply.github.com>
Proposed changes (including videos or screenshots)
Issue(s)
LOG-3
Steps to test or reproduce
Further comments