You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is better not to fix it to email, because there are cases where email is not used.
I will create a pull request, any other ideas or opinions?
thank you
The text was updated successfully, but these errors were encountered:
No change was made following #422 from what I can see.
You could raise a PR that addresses this, but it's a bigger problem than just created_by_user_email.
In a potential change, created_by_user_email should be renamed because what this is actually doing is providing a way to identify which user is associated to something in the templates. But obviously created_by_user_id or something would make you expect a number for the user's ID, when infact what we're looking for here is an identifier for a user.
There is more functionality in the app that expects a user to have an email address, so that would need to be fixed as well if we're going to bring support for users without an email address.
I am using a custom user that inherits from AbstractBaseUser and I get an AttributeError.
The reason is that the email is referenced in the created_by_user_email method of the QueryForm.
I think it is better not to fix it to email, because there are cases where email is not used.
I will create a pull request, any other ideas or opinions?
thank you
The text was updated successfully, but these errors were encountered: