FEAT: Sign Up flow

[nikita-remeslov]

What feature?

• Add name column to users table through migration
• Update model
• Update service to save user
• Use encryption service to hash user password before saving to the db
• Add /auth/sign-up endpoint to the controller
• Return object with user property in response (exclude password_hash and password_salt columns)
• Add validation (check with the dev who is implementing FE task)

Acceptance criteria

Following this Test Cases: https://docs.google.com/spreadsheets/d/1b-xRyyn39r4N9k-P7zC618jotIVunZbbz1Vv9ipHNOM/edit?gid=1854802596#gid=1854802596

• The migration runs successfully without errors in all environments.
• Passwords are hashed using the encryption service before being stored in the database.
• The user service ensures that the password_hash and password_salt columns are excluded from the returned user object.
• A new /auth/sign-up endpoint is added to the controller.
• After successful sign-up, the endpoint returns a user object with id, email, fullName, and token, excluding password_hash and password_salt.

[nikita-remeslov]

Check it please - #4 (comment)

[DaniellaZambrano]

@JPjok3r How do you test the APIs on Swagger to make requests on the sign-up route?

[JPjok3r]

Hi @DaniellaZambrano this is needed to test from swagger, { "fullName": "John Doe", "email": "[email protected]", "password": "string", "confirmPassword": "string" } this example data object structure should be sent to the endpoint for a successful store in database and receive status: 200, and for error the same as in FE.

[DaniellaZambrano]

@JPjok3r take a look

[JPjok3r]

@DaniellaZambrano well acording what we have, the url should be "http://localhost:3001/api/v1/auth/sign-up", and in the body is missing confirmPassword

[DaniellaZambrano]

@JPjok3r That’s how it is in Swagger; I’m not sure who added it that way, but those are the fields that are currently there. I can't add fields I’m not familiar with. If you check Swagger, you’ll see there isn’t more information available.

[JPjok3r]

@DaniellaZambrano yes I was checking that, in sign-in is the same, who was in charge of that task, and here you can add fields, when you click on Try it out button and before clicking on execute

But anyway I saw the url is wrong, that is why you are getting 404 "not found"

[DaniellaZambrano]

@JPjok3r can you give me the steps by steps to reproduce it?

[JPjok3r]

Yes sure @DaniellaZambrano :

1. Click on Try it out button

2. Click anywhere in the area where the data is printed

3. Then click execute.
   I saw Sanchousina is updating the documentation, but her Pull Request hasn't been merged yet, so maybe you will still getting 404.

[DaniellaZambrano]

@JPjok3r I'm not talking about that. I need is the URL you use and settings from localhost

[DaniellaZambrano]

Postman response: