incremental-social/incremental-social
incremental-social/incremental-social
2
0
Fork 0
Code Issues 30 Pull requests Projects Activity

Remove first and last name fields #5

New issue
Closed
opened 2023-09-24 00:07:03 +00:00 by thepaperpilot · 3 comments
thepaperpilot commented 2023-09-24 00:07:03 +00:00
Owner
Copy link

https://github.com/zitadel/zitadel/issues/4386

https://github.com/zitadel/zitadel/issues/4386 - [ ] Get this PR merged: <https://github.com/zitadel/zitadel/pull/4988> - [ ] Get this issue resolved: <https://github.com/zitadel/zitadel/issues/5333> - [ ] Get this issue resolved: <https://github.com/zitadel/zitadel/issues/6124> - [ ] Make example user schema: <https://github.com/zitadel/zitadel/issues/6433> (In Progress)
thepaperpilot added this to the 1.0 milestone 2023-09-24 00:07:03 +00:00
thepaperpilot added this to the Homepage project 2023-09-24 00:07:03 +00:00
thepaperpilot modified the project from Homepage to Auth 2023-09-24 04:05:54 +00:00
thepaperpilot commented 2023-12-07 22:55:49 +00:00
Author
Owner
Copy link

Also make email readonly

Also make email readonly
thepaperpilot changed title from Make first and last names optional to Remove first and last name fields 2024-01-24 17:10:02 +00:00
thepaperpilot commented 2024-01-25 03:52:16 +00:00
Author
Owner
Copy link

I think this can be considered close enough for now. I've used an action to copy the username to all name fields, which should prevent the core issue of users having their full names as their display name on Cinny and forgejo.

The email not being readonly is sub-optimal but since it requires re-verification when changed I think it's fine for now. I'll make it readonly once zitadel releases the user scheme later this year.

I think this can be considered close enough for now. I've used an action to copy the username to all name fields, which should prevent the core issue of users having their full names as their display name on Cinny and forgejo. The email not being readonly is sub-optimal but since it requires re-verification when changed I think it's fine for now. I'll make it readonly once zitadel releases the user scheme [later this year](https://zitadel.com/blog/upcoming-features-2024).
thepaperpilot modified the milestone from 1.0 to 1.1 2024-01-25 03:52:30 +00:00
thepaperpilot modified the milestone from 1.1 to 1.0 2024-01-27 07:13:04 +00:00
thepaperpilot commented 2024-01-27 13:38:43 +00:00
Author
Owner
Copy link

Got dev env working and successfully removed the undesired fields!

Got dev env working and successfully removed the undesired fields!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
1.0
Projects
Clear projects
No items
No project
Auth
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: incremental-social/incremental-social#5
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?