CRUD Person

[georgebejan]

Currently we have the User entity which holds authentication information.
We also need a profile for each user. This profile will be filled after the account is created.
In order to hold information about this, we need a Person entity with the following attributes:

• first name
• last name
• address (street name, street number, ap. number, city, county, country, zip code)

There should be a OneToOne connection between a Person and an User

Create the full CRUD functionality (controller, service, repository, entity) and add tests for it

[calin-buzetelu]

I would like to work on this one if it is possible, but I think I will need a little help with the repository part

[iccaprar]

I can help with the backend repo part.

[iccaprar]

Pot incepe eu partea aceasta.

[iccaprar]

Before starting the data model, do we have a single address for the person or multiple addresses? I need to know whether to have the address embedded in the person or as a separate entity with a 1:n relation.