fix: update WorkspaceOwnerName to use user.name instead of user.username (#18025)

We have been using the user.username instead of user.name in wrong
places, making it very confusing for the UI.
This commit is contained in:
Bruno Quaresma
2025-05-27 11:42:07 -03:00
committed by GitHub
parent 9827c97f32
commit d63417b542
24 changed files with 579 additions and 90 deletions
+7 -3
View File
@@ -8408,7 +8408,8 @@ If the schedule is empty, the user will be updated to use the default schedule.|
"workspace_name": "string",
"workspace_owner_avatar_url": "string",
"workspace_owner_id": "e7078695-5279-4c86-8774-3ac2367a2fc7",
"workspace_owner_name": "string"
"workspace_owner_name": "string",
"workspace_owner_username": "string"
},
"name": "string",
"next_start_at": "2019-08-24T14:15:22Z",
@@ -9375,7 +9376,8 @@ If the schedule is empty, the user will be updated to use the default schedule.|
"workspace_name": "string",
"workspace_owner_avatar_url": "string",
"workspace_owner_id": "e7078695-5279-4c86-8774-3ac2367a2fc7",
"workspace_owner_name": "string"
"workspace_owner_name": "string",
"workspace_owner_username": "string"
}
```
@@ -9406,6 +9408,7 @@ If the schedule is empty, the user will be updated to use the default schedule.|
| `workspace_owner_avatar_url` | string | false | | |
| `workspace_owner_id` | string | false | | |
| `workspace_owner_name` | string | false | | |
| `workspace_owner_username` | string | false | | |
#### Enumerated Values
@@ -10082,7 +10085,8 @@ If the schedule is empty, the user will be updated to use the default schedule.|
"workspace_name": "string",
"workspace_owner_avatar_url": "string",
"workspace_owner_id": "e7078695-5279-4c86-8774-3ac2367a2fc7",
"workspace_owner_name": "string"
"workspace_owner_name": "string",
"workspace_owner_username": "string"
},
"name": "string",
"next_start_at": "2019-08-24T14:15:22Z",