🐛 Bug Report: users.*.update trigger function - Inconsistent request payload

[Irutom]

👟 Reproduction steps

I am experiencing an issue with the users.*.update trigger function. I've noticed that the payload data provided in the trigger event is inconsistent, particularly when different types of user information are updated.

When an email update occurs, the payload contains the full user object.

👍 Expected behavior

When an email update occurs, the payload contains the full user object.

 "x-appwrite-event": "users.656ae11125ca984676a9.update",
 {
  "body": {
      "$id": "656ae11125ca984676a9",
      "$createdAt": "2023-12-02T07:47:29.156+00:00",
      "$updatedAt": "2023-12-02T18:52:15.750+00:00",
      "name": "",
      "password": "..",
      "hash": "argon2",
      "hashOptions": {
          "type": "argon2",
          "memoryCost": 2048,
          "timeCost": 4,
          "threads": 3
      },
      "registration": "2023-12-02T07:47:29.155+00:00",
      "status": true,
      "labels": [],
      "passwordUpdate": "2023-12-02T07:47:29.155+00:00",
      "email": "[email protected]",
      "phone": "",
      "emailVerification": false,
      "phoneVerification": false,
      "prefs": {
          "test": "value"
      },
      "accessedAt": "2023-12-02T07:47:29.155+00:00"
  },
 }
...

👎 Actual Behavior

Conversely, when a user preference is updated, the payload only contains the preference object, not the full user object.

"x-appwrite-event": "users.656ae11125ca984676a9.update",
{
    "body": {
        "test": "value",
        "test2": "val2"
    },
  ...
}

### 🎲 Appwrite version

Version 1.4.x

### 💻 Operating system

MacOS

### 🧱 Your Environment

Docker installation on mac. Function runtime node-18.0.

### 👀 Have you spent some time to check if this issue has been raised before?

- [X] I checked and didn't find similar issue

### 🏢 Have you read the Code of Conduct?

- [X] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)

[stnguyen90]

@urioanmot, thanks for creating this! Let me check with the team.

[stnguyen90]

We'll want to update the users api to return the user object for consistency.

[nick2432]

can i work on this?

[stnguyen90]

For now, we want to fix the users API to return the user object for consistency.

@nick2432 assigning to you now! Thanks for your patience!

[Irutom]

@nick2432 When a user preference is updated, the payload only contains the preference object, not the full user object as mentioned in the bug report.

[Irutom]

@nick2432 It appears that the API call shown in the video is made from the dashboard UI to the server. If yes, that might not be the right place. Actual issue is with the request payload received on users.*.update event (cloud function), which needs to be consistent when updating user preferences vs other fields as mentioned in the bug description.

https://appwrite.io/docs/advanced/platform/events

[nick2432]

@nick2432 It appears that the API call shown in the video is made from the dashboard UI to the server. If yes, that might not be the right place. Actual issue is with the request payload received on users.*.update event (cloud function), which needs to be consistent when updating user preferences vs other fields as mentioned in the bug description.

https://appwrite.io/docs/advanced/platform/events

ok