improvement: 태그 관리 API 프론트엔드 연동 수정 (#267) #268
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#268
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "improvement/#267-tag-api-frontend-fix"
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?
📋 작업 요약
tag_index필드 추가 (서비스별 순번 동적 계산)service_id필드 추가X-Service-Code헤더 없이 전체 서비스 태그 조회 지원🔗 관련 이슈 (Related Issues)
Closes #267
🛠️ 작업 내용 (Changes)
SPMS.Application/DTOs/Tag/TagListResponseDto.cs— TagSummaryDto에 tag_index 필드 추가SPMS.Application/Services/TagService.cs— GetListAsync에서 서비스별 Id 순서 기준 1-based 순번 동적 계산SPMS.Application/DTOs/Service/ServiceListResponseDto.cs— ServiceSummaryDto에 ServiceId 추가SPMS.Application/DTOs/Service/ServiceResponseDto.cs— ServiceResponseDto에 ServiceId 추가SPMS.Application/Services/ServiceManagementService.cs— MapToSummaryDto, MapToDto 매핑에 ServiceId 추가SPMS.API/Middlewares/ServiceCodeMiddleware.cs— OPTIONAL_FOR_ADMIN에 /v1/in/tag 경로 추가📢 리뷰어 참고 사항 (To Reviewers)
✅ 체크리스트 (Self Checklist)
📸 스크린샷 / 테스트 로그 (Screenshots/Logs)
빌드 성공: 경고 0개, 오류 0개