-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
chore: Remove incorrect and unused update
signature
#33529
Conversation
Failed server tests
|
WalkthroughWalkthroughThe recent updates enhance the Changes
Recent Review DetailsConfiguration used: CodeRabbit UI Files selected for processing (1)
Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
.flatMap(user -> update(user.getId(), updates, User.Fields.id) | ||
.flatMap(user -> updateWithoutPermission(user.getId(), updates) |
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.
UserServiceCE
is the only service that overrides the update
method, to do a permission check, and has its own updateWithoutPermission
separately. I intend to fix that inconsistency as well, in a separate PR.
The
update
method withString, T, String
signature, is not used in it's form anywhere. This is most likely owing to the implementation being off. The criteria used to find the object to be updated, is not the same as the criteria used to find the updated object to return to the caller.The query to update is
{value of key field} = id
.The query to find is
{value of "id" field} = id
.This discrepency is likely why this function is not used anywhere. The
ApplicationServiceCE
alone has an overridden implementation for this signature, but that's defined with different variable names, and treats the third argument as the Git branch name, notkey
. That function is indeed used, and is unaffected by this change.All of above is verified on EE as well. No conflicts, no build failure.
/ok-to-test tags="@tag.Sanity"