Please fix names in replit identity cli

The names in replit identity don’t follow any convention.

This is the result of verifying token:

{
  replid: '358b3972-aced-41c3-b888-163fdb350c79',
  user: '7heMech',
  slug: 'Replit-Identity',
  aud: '358b3972-aced-41c3-b888-163fdb350c79',
  user_id: 6759741,
  Runtime: { Interactive: { cluster: 'global', subcluster: 'interactive' } }
}

My eyes just hurt by looking at it, I would at least like for replid to be like user_id

I don’t understand why an id consisting of numbers and letters is worse than an id consisting only of numbers?

1 Like

That wasn’t Mech’s issue look at the key names:

2 Likes

it doesn’t stop there. For the python port I literally had to fix their code cuz They thought they had consistent naming conventions but I did bug testing and noticed it’s not consistent (hehe officially I got the change pushed so I can say bug hunter for replit :smirk:). Furthermore, I found that when I used it for a bounty it would constantly do weird things and put the repl id in multiple different keys

3 Likes

Mhm, my example is from the cli tool, I have a package for JS and I’ve made it recognize and parse them into JS notation, but for the replid, how can it even recognize it’s two words? I had to fix that manually temporarily, and it looks like this:

{
  userId: 6759741,
  replId: '358b3972-aced-41c3-b888-163fdb350c79',
  user: '7heMech',
  slug: 'Replit-Identity',
  aud: '358b3972-aced-41c3-b888-163fdb350c79',
  runtime: { interactive: { cluster: 'global', subcluster: 'interactive' } }
}
3 Likes

yeah same it would put like repl_id, replid, replId lol it was so many

3 Likes

Hmm, it would help if they just made the cli tool open source, so we can make some PRs

1 Like

Has anyone recently played with identity, I think they might have improved the reliability.
I have an implementation of replit database which requires auth with replit identity for writing, might make it into a challenge.