feat: Refactor User entity and datasource to use email and password hashing with salt
This commit is contained in:
@@ -140,14 +140,14 @@ export interface UserDto {
|
||||
createdAt: string;
|
||||
updatedAt: string;
|
||||
lastEditorID: string;
|
||||
username: string;
|
||||
email: string;
|
||||
password: string; // Note: In a real application, you would NEVER send the password in a DTO. This is just for demonstration.
|
||||
role: string;
|
||||
companyId: number /* int */;
|
||||
hourlyRate: number /* float64 */;
|
||||
}
|
||||
export interface UserCreateDto {
|
||||
username: string;
|
||||
email: string;
|
||||
password: string; // Note: In a real application, you would NEVER send the password in a DTO. This is just for demonstration.
|
||||
role: string;
|
||||
companyId: number /* int */;
|
||||
@@ -158,7 +158,7 @@ export interface UserUpdateDto {
|
||||
createdAt?: string;
|
||||
updatedAt?: string;
|
||||
lastEditorID?: string;
|
||||
username?: string;
|
||||
email?: string;
|
||||
password?: string; // Note: In a real application, you would NEVER send the password in a DTO. This is just for demonstration.
|
||||
role?: string;
|
||||
companyId?: number /* int */;
|
||||
|
||||
Reference in New Issue
Block a user