Currently, when creating a user via the /auth/access_token endpoint, if the name field is null, it causes issues during the user creation process. To resolve this, we need to update the logic so that if the name is null, the githubId should be saved in the name field.
Requirements
Modify the /auth/access_token endpoint to check if the name is null.
If name is null, use the githubId value to populate the name field.
Ensure that this logic is applied only during the user creation process.
Acceptance Criteria
The name field is populated with the githubId if the name is null during user creation.
The issue causing the user creation process to fail due to a null name is resolved.
Ensure no other parts of the system are affected by this change.
Additional Notes
Test this scenario with different cases (e.g., valid name, nullname, etc.) to ensure the logic works as expected.
Update any necessary documentation to reflect this change.
Currently, when creating a user via the
/auth/access_token
endpoint, if thename
field isnull
, it causes issues during the user creation process. To resolve this, we need to update the logic so that if thename
isnull
, thegithubId
should be saved in thename
field.Requirements
/auth/access_token
endpoint to check if thename
isnull
.name
isnull
, use thegithubId
value to populate thename
field.Acceptance Criteria
name
field is populated with thegithubId
if thename
isnull
during user creation.null
name is resolved.Additional Notes
name
,null
name
, etc.) to ensure the logic works as expected.