From ab2281d7e77912e1e11a6b491773595d7a835c6d Mon Sep 17 00:00:00 2001
From: Thomas Heartman <thomas@getunleash.io>
Date: Sat, 16 Dec 2023 08:28:22 +0100
Subject: [PATCH] fix: make username nullable in user-schema (#5656)

I noticed I was getting warnings logged in my local instance when
visiting the users page (`/admin/users`)

```json
{
    "schema": "#/components/schemas/publicSignupTokensSchema",
    "errors": [
        {
            "instancePath": "/tokens/0/users/0/username",
            "schemaPath": "#/components/schemas/userSchema/properties/username/type",
            "keyword": "type",
            "params": {
                "type": "string"
            },
            "message": "must be string"
        }
    ]
}
```

It was complaining because one of my users doesn't have a username, so
the value returned from the API was:

```json
{
    "users": [
        {
            "id": 2,
            "name": "2mas",
            "username": null
        }
    ]
}
```

This adjustment fixes that oversight by allowing `null` values for the
username.
---
 src/lib/openapi/spec/user-schema.ts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/lib/openapi/spec/user-schema.ts b/src/lib/openapi/spec/user-schema.ts
index d41c50beb4..31a1535752 100644
--- a/src/lib/openapi/spec/user-schema.ts
+++ b/src/lib/openapi/spec/user-schema.ts
@@ -36,6 +36,7 @@ export const userSchema = {
             description: 'A unique username for the user',
             type: 'string',
             example: 'hunter',
+            nullable: true,
         },
         imageUrl: {
             description: `URL used for the userprofile image`,