The User model has a LastLogin Date property that will store the last login date for the user. The issue is when using the Entity Framework Core Migrations that the LastLogin field is required to have a value. This should change to allow null values for the reason that when a user is created they have never logged on before.
This issue can be fixed by looking at the UserContext class and explicitly state that the LastLogin property to allow nulls. This will allow the completion of Issue #28. By default if the user has never logged in then they should be required to verify the credentials that they registered with are valid. This will require an email to be sent to the email address that the user has registered with to verify that the email address has been verified. For now the email address will be the only way of validating the user during the registration phase, eventually phone numbers will be next.
The [User](https://github.com/amazing-username/Icarus/blob/master/Models/User.cs) model has a LastLogin Date property that will store the last login date for the user. The issue is when using the Entity Framework Core Migrations that the LastLogin field is required to have a value. This should change to allow null values for the reason that when a user is created they have never logged on before.
This issue can be fixed by looking at the [UserContext](https://github.com/amazing-username/Icarus/blob/master/Models/Context/UserContext.cs) class and explicitly state that the LastLogin property to allow nulls. This will allow the completion of Issue #28. By default if the user has never logged in then they should be required to verify the credentials that they registered with are valid. This will require an email to be sent to the email address that the user has registered with to verify that the email address has been verified. For now the email address will be the only way of validating the user during the registration phase, eventually phone numbers will be next.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The User model has a LastLogin Date property that will store the last login date for the user. The issue is when using the Entity Framework Core Migrations that the LastLogin field is required to have a value. This should change to allow null values for the reason that when a user is created they have never logged on before.
This issue can be fixed by looking at the UserContext class and explicitly state that the LastLogin property to allow nulls. This will allow the completion of Issue #28. By default if the user has never logged in then they should be required to verify the credentials that they registered with are valid. This will require an email to be sent to the email address that the user has registered with to verify that the email address has been verified. For now the email address will be the only way of validating the user during the registration phase, eventually phone numbers will be next.