DOPΣ - what if there is conflict in githubhandl...
what if there is conflict in github_handle and tscircuit_handle
7 Replies
the user will have to create a handle
if you want for laziness you can just keep incrementing like old xbox usernames e.g.
seveibar2 seveibar3 until one works
the user should be able to rename from their settings
(the incrementing would happen on the backend)
technically the best approach is to have the frontend do
/accounts/check_if_username_available?tscircuit_handle
then error and make the user select a new oneOk for routing purposes, are we switching to tscircuit handles? Or keep as GitHub handles only?
Tscircuit handles
Github handles are just metadata now
What if the user hasn't set tscircuit handle? For current users are we going to do some migration kinda stuff?
And why is tscircuit handle nullable for account then if it's req for account to be viewed?
We do need a migration page on the backend
It eventually will not be nullable
Great questions
Yes we do need a migration page
(On admin)
Any eta? So I should start routing revamping stuff
Also can we add some route like /get-acc-or-org to avoid double request /acc/get & /org/get
For tscircuit handles
Or should we just fetch /org/get and check if personal
Yea just /org/get yea
Want to make the migration page and test for backend?