[BE] Controller 분리가 필요할 것 같다.

[gitchannn]

현재 하나의 컨트롤러 안에서 컨트롤러 이름에 들어간 도메인과 관련없거나, 내부적으로 서로 일관성 없는 메서드들이 마구마구 들어있는 경우가 많습니다. 예를 들어 밑에 있음.
정리가 좀 필요할 것 같습니다.

@RequiredArgsConstructor
@RestController
@RequestMapping("/api")
public class CouponApiController {

    private final CouponService couponService;

    @GetMapping("/cafes/{cafeId}/customers")
    public ResponseEntity<CafeCustomersFindResponse> findCustomersByCafe(@PathVariable Long cafeId) {
        List<CafeCustomerFindResultDto> coupons = couponService.findCouponsByCafe(cafeId);
        List<CafeCustomerFindResponse> cafeCustomerFindResponses = coupons.stream()
                .map(CafeCustomerFindResponse::from)
                .toList();

        return ResponseEntity.ok(new CafeCustomersFindResponse(cafeCustomerFindResponses));
    }

    @GetMapping("/customers/{customerId}/coupons")
    public ResponseEntity<CustomerAccumulatingCouponsFindResponse> findCustomerUsingCouponByCafe(
            @PathVariable Long customerId,
            @RequestParam Long cafeId,
            @RequestParam boolean active
    ) {
        List<CustomerAccumulatingCouponFindResultDto> accumulatingCoupon = couponService.findAccumulatingCoupon(cafeId, customerId);

        List<CustomerAccumulatingCouponFindResponse> accumulatingResponses = accumulatingCoupon.stream()
                .map(CustomerAccumulatingCouponFindResponse::from)
                .toList();

        return ResponseEntity.ok(new CustomerAccumulatingCouponsFindResponse(accumulatingResponses));
    }

    @PostMapping("/customers/{customerId}/coupons")
    public ResponseEntity<CouponCreateResponse> createCoupon(
            @RequestBody @Valid CouponCreateRequest request,
            @PathVariable("customerId") Long customerId
    ) {
        Long couponId = couponService.createCoupon(request.getCafeId(), customerId);
        return ResponseEntity.status(HttpStatus.CREATED).body(new CouponCreateResponse(couponId));
    }

    @PostMapping("/customers/{customerId}/coupons/{couponId}/stamps/{ownerId}")
    public ResponseEntity<Void> createStamp(
            @PathVariable Long customerId,
            @PathVariable Long couponId,
            @PathVariable Long ownerId,
            @RequestBody @Valid StampCreateRequest request
    ) {
        StampCreateDto stampCreateDto = new StampCreateDto(ownerId, customerId, couponId, request.getEarningStampCount());
        couponService.createStamp(stampCreateDto);
        return ResponseEntity.status(HttpStatus.CREATED).build();
    }
}

[gitchannn]

1. api > admin
2. application > admin
3. customer를 위한 클래스는 api, application 패키지 바로 아래
4. entity는 분리하지 않음
5. admin controller, service는 앞에 Admin을 붙인다.
   예. AdminCouponFindApiController

[gitchannn]

api, application에서 명렁과 조회는 클래스를 분리하자!

예.
조회 -> CouponFindApiController
아래 createCoupon, createStamp과 같이 상태에 변화를 주는 것 -> CouponCommandApiController