Description

The new user admin preference query fields added in #3551 (addressing #479) are read-only. The original issue also mentions supporting these fields in createUser and updateUser mutations.

This issue tracks adding mutation (write) support for the 4 user admin preference fields.

Fields to Support in Mutations

Example Mutation

mutation {
  updateUser(input: {
    id: "dXNlcjox"
    adminColor: "midnight"
    hasRichEditingEnabled: false
    hasSyntaxHighlightingEnabled: true
    hasCommentShortcutsEnabled: true
  }) {
    user {
      adminColor
      hasRichEditingEnabled
      hasSyntaxHighlightingEnabled
      hasCommentShortcutsEnabled
    }
  }
}

Implementation Notes

• Input fields should be added to UserInput (for createUser) and UpdateUserInput (for updateUser)
• Use update_user_option() to persist values (consistent with query resolution using get_user_option() per feat: add core user admin preferences fields to User type #3551)
• Boolean inputs should be stored as WordPress string values ('true' / 'false')
• adminColor could optionally validate against registered admin color schemes via wp_admin_css_color()
• Permission checks should ensure only the user themselves or an admin can update these preferences

Acceptance Criteria

• updateUser mutation accepts the 4 new input fields
• createUser mutation accepts the 4 new input fields
• Values persist correctly via update_user_option()
• Boolean fields correctly convert GraphQL Boolean to WordPress string storage
• Permission model respects existing updateUser capabilities
• Unit tests cover: setting values, default behavior, permission checks
• PHPCS and PHPStan pass

Related

• Partially completes Add core user meta to the User Type #479
• Builds on feat: add core user admin preferences fields to User type #3551