The discussion highlights an inconsistency in the UserUpdater class where updating a user’s custom field using a symbol key (e.g., :user_field_1) results in duplicate entries in the database, while using a string key (e.g., 'user_field_1') correctly replaces the existing value. fzngagan reproduces the issue by calling UserUpdater#update with a hash containing a symbol key, which causes the value to be appended as a comma-separated string in the UI. In contrast, wrapping the parameters in ActionController::Parameters and permitting them behaves correctly, though it’s considered unnatural. fzngagan traces the root cause to the HasCustomFields mixin, which treats symbol and string keys differently — symbol keys trigger creation of new UserCustomField records, while string keys delete existing ones before inserting the new value. A PR (#10486) was submitted and merged to resolve this inconsistency, ensuring consistent behavior regardless of key type. eviltrout acknowledges the issue as valid and thanks the reporter for identifying it.