Repository Implementation Decision

After consulting with one of the teachers regarding best practices for accessing the database, it was suggested to create an implementation class for the repository interface to ensure adherence to dependency injection principles. However, I opted not to follow this approach.

Given that the repository methods do not require additional business logic and instead rely purely on simple query annotations, implementing an additional class felt redundant. The use of interface-level query annotations effectively achieves the desired functionality without adding unnecessary complexity.

com/fontys/crowdfund/persistence/UserRepository.java

package com.fontys.crowdfund.persistence;

import com.fontys.crowdfund.persistence.dto.OutputDTOUser;
import com.fontys.crowdfund.persistence.entity.UserEntity;
import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.data.jpa.repository.Modifying;
import org.springframework.data.jpa.repository.Query;
import org.springframework.data.repository.query.Param;

import java.util.List;

public interface UserRepository extends JpaRepository<UserEntity, Long> {

        // Check if a user exists by email
        boolean existsByEmail(String email);

        // Check if a user exists by ID
        boolean existsById(int userId);

        // Find a user by ID
        UserEntity findById(int userId);

        // Find a user by email
        @Query("SELECT u " +
                        "FROM UserEntity u " +
                        "WHERE u.email = :userEmail")
        UserEntity findByEmail(@Param("userEmail") String userEmail);

        // Delete a user by ID
        @Modifying
        @Query("DELETE " +
                        "FROM UserEntity u " +
                        "WHERE u.id = :userId")
        void deleteById(@Param("userId") int userId);

}