feat: ApiResponse<T> 공통 응답 포맷 구현 (#14) #15
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#15
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/#14-api-response"
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?
📋 작업 요약
ApiResponse<T>래퍼 클래스 구현Success(data)/Fail(code, msg)정적 팩토리 메서드 제공ApiResponse<T>)과 비제네릭(ApiResponse) 두 가지 버전 지원🔗 관련 이슈 (Related Issues)
Closes #14
🛠️ 작업 내용 (Changes)
SPMS.Domain/Common/ApiResponse.cs— 공통 응답 래퍼 클래스 (result,code,msg,data)ApiResponse.Success()/ApiResponse.Fail(code, msg)— 데이터 없는 응답용ApiResponse<T>.Success(data)/ApiResponse<T>.Fail(code, msg)— 데이터 포함 응답용System.Text.Json.SerializationJsonPropertyName으로 camelCase JSON 직렬화📢 리뷰어 참고 사항 (To Reviewers)
init접근자 사용으로 생성 후 불변(immutable) 보장✅ 체크리스트 (Self Checklist)
📸 스크린샷 / 테스트 로그 (Screenshots/Logs)