-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate slugs for all users #73
Comments
@crysfel, how do you feel about only using the |
I'm ok with that, the only thing is we will have to deploy the FE and BE at the same time. That's why I was thinking on supporting both fields, but I don't think this is a big issue. |
ohhh, right. Great point. Then my idea is bad for the short term. How do you feel about moving to a "slug only" approach eventually? As in, after the FE is no longer using the |
Yes, totally. I think it will make our lives easier to maintain a single ID key |
I believe that with nextjs so the server is not responsible on serving the FE, this task is no longer relevant. |
We need to generate a slug for all users in the database (and all new users), we are going to use it to create links in the FE for their profile pages.
slug
field, it should be unique and indexed in the database.slug
or_id
The text was updated successfully, but these errors were encountered: