improvement: 메시지 발송 상태 집계 규칙 고정 (#178) #228
No reviewers
SPMS/Owners
Labels
No Label
Priority
High
Priority
Low
Priority
Medium
Priority
Non
Priority
Urgent
Status
Available
Status
Done
Status
In Progress
Type
Bug
Type
Chore
Type
Design
Type
Documentation
Type
Feature
Type
Improvement
Type
Refactor
Type
Research
Type
Task
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SPMS/SPMS_API#228
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "improvement/#178-send-status-rule"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 작업 요약
SendStatusstatic class로 분리하여 단일 진실 공급원(Single Source of Truth) 확보🔗 관련 이슈 (Related Issues)
Closes #178
🛠️ 작업 내용 (Changes)
SPMS.Domain/Enums/SendStatus.cs— 상수 3종(Pending/Complete/Failed) + Determine() 정적 메서드 신규 생성SPMS.Application/Services/MessageService.cs— private DetermineSendStatus() 삭제 → SendStatus.Determine() 호출SPMS.Infrastructure/Persistence/Repositories/MessageRepository.cs— 매직 스트링 → SendStatus 상수 참조SPMS.API/Controllers/MessageController.cs— list/info Swagger Description에 SendStatus 규칙 안내 추가📢 리뷰어 참고 사항 (To Reviewers)
✅ 체크리스트 (Self Checklist)
📸 스크린샷 / 테스트 로그 (Screenshots/Logs)