James Makela comments

Results 7 comments of


                                            James Makela

bug: Setup process allows you to create more than one superuser with the same email.

No worries. I would be keen to tackle this one over the weekend if I could please be assigned?

fix: Change `User` class in `backend/models.py` to use email as uniqu…

Hi Trey, unfortunately I am flat out for the next couple of weeks. I could continue after that. However if you or anyone else wants to take over that is...

fix: Change `User` class in `backend/models.py` to use email as uniqu…

Update: - The issues with this change I have identified so far seem to go away after refreshing the page once or twice. Next Steps: - Manual testing of program...

fix: Change `User` class in `backend/models.py` to use email as uniqu…

> Hey @James-Makela, what you said sounds good. As for the user class, we have a custom one already in models.py so you can override parts of that if that's...

fix: Change `User` class in `backend/models.py` to use email as uniqu…

Hi Trey, I made a little progress on this. I have extended the `CustomUserManager` class, and been able to get the superuser creation working with only email. However going into...

fix: Change `User` class in `backend/models.py` to use email as uniqu…

Trying that, with the whole user class as: ```python class User(AbstractUser): objects = CustomUserManager() # type: ignore email = models.EmailField(max_length=150, unique=True) username = models.CharField(max_length=150, unique=True) USERNAME_FIELD = "email" REQUIRED_FIELDS =...

fix: Change `User` class in `backend/models.py` to use email as uniqu…

I notice backend/views/core/auth/create_account.py at line 81 sets the username to be the email. Changing the overridden `_create_user` function to do the same seems to work perfectly so far. `_create_user` function:...