Task/add location object

[SelahattinSert]

Add location object without unit tests

[ozgen]

I added few comments @SelahattinSert

[SelahattinSert]

Would it be better if i add new service for the location and handle the write operation to the database separately? @ozgen

[ozgen]

Would it be better if i add new service for the location and handle the write operation to the database separately? @ozgen

no could you read the documentations @SelahattinSert

ref: https://docs.spring.io/spring-framework/reference/data-access/transaction/declarative/annotations.html

https://www.geeksforgeeks.org/spring-boot-transaction-management-using-transactional-annotation/

[SelahattinSert]

I am sorry about commit mess @ozgen

[ozgen]

I didn't find any problem in your code @SelahattinSert,
you can start to write unit tests.

[SelahattinSert]

I added unit tests @ozgen

[ozgen]

looks good to me @SelahattinSert

I am very busy in these days, I will create another issue when I am available,
thanks for your patience

[ozgen]

your assert usage is okay for me, however, you can also use it like this:

assertThat(location)
    .isNotNull()
    .satisfies(loc -> {
        assertThat(loc.getLatitude())
            .as("Check Latitude")
            .isNotNull()
            .isEqualTo(LATITUDE);

        assertThat(loc.getLongitude())
            .as("Check Longitude")
            .isNotNull()
            .isEqualTo(LONGITUDE);

        assertThat(loc.getAddress())
            .as("Check Address")
            .isNotNull()
            .isEqualTo(ADDRESS);
    });

Because this approach allows chains multiple assertions directly related to the location. This reduces redundancy and improves readability.

[SelahattinSert]

I was busy too, this week and the following week are my midterm weeks. Sorry if i took so long and thanks for your patience too @ozgen