Not persisting hours after creating them with the in-memory repository

[msamoylov]

So, you're creating a new Hour, but returning it immediately without storing it in the map.

wild-workouts-go-ddd-example/internal/trainer/adapters/hour_memory_repository.go

Line 40 in 22c0a25

return m.hourFactory.NewNotAvailableHour(hourTime)

It looks like ok will be always false.

wild-workouts-go-ddd-example/internal/trainer/adapters/hour_memory_repository.go

Line 38 in 22c0a25

currentHour, ok := m.hours[hourTime]

Am I missing something here?

[roblaszczak]

That should be documented better 😉.

In general, the idea is, that the repository should be independent of the database, but be rather some domain concept. By example it will be probably more clear:

In practice (not in the database, in reality) hour exists, even if it was not persisted. So for example, if we didn't persist 14:00 it exists anyway and is available for training. So that's why it is not persisted in GetHour.

If we want to persist it, we need to explicitly call UpdateHour. This is also how it works for all other implementations.

Does it make sense for you?

[msamoylov]

What I was saying, is that you're just returning a newly created hour without putting it to the map.

wild-workouts-go-ddd-example/internal/trainer/adapters/hour_memory_repository.go

Line 40 in 22c0a25

return m.hourFactory.NewNotAvailableHour(hourTime)

This should be IMO:

        currentHour, err := m.hourFactory.NewNotAvailableHour(hourTime) 
        // Handle error, skipped
        m.hours[hourTime] = *currentHour

Otherwise your in-memory storage doesn't make much sense.

[m110]

@msamoylov It's persisted in the UpdateHour method:

wild-workouts-go-ddd-example/internal/trainer/adapters/hour_memory_repository.go

Line 66 in 22c0a25

m.hours[hourTime] = *updatedHour

The result of GetHour is returned to the frontend application, which shows the hour as empty, if it's not filled in the database. The user can then click a button to fill it.