[Feature/#95] 캠페인 목록 조회 및 전체 캠페인 제어 API 연동 - #99
Merged
Merged
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthrough조직 워크스페이스 조회 후 첫 조직을 선택해 캠페인 목록을 불러오고, 전체 캠페인 상태(ON_GOING/PAUSED) 일괄 제어 API를 추가해 UI와 상태 흐름을 연동했습니다. 타입과 Campaign 컴포넌트 Props가 재설계되어 목록 렌더링이 변경되었습니다. Changes
Sequence Diagram(s)sequenceDiagram
actor User
participant AdsListPage as AdsListPage (UI)
participant API as Ads API Layer
participant Backend as Backend
User->>AdsListPage: 페이지 진입
AdsListPage->>API: getMyWorkspaces()
API->>Backend: GET /workspaces
Backend-->>API: workspaces[]
API-->>AdsListPage: workspaces
AdsListPage->>AdsListPage: currentOrgId = first workspace
AdsListPage->>API: getCampaignList(currentOrgId)
API->>Backend: GET /api/project/{orgId}
Backend-->>API: campaigns[]
API-->>AdsListPage: ICampaign[]
User->>AdsListPage: "모두 일시정지" 클릭
AdsListPage->>API: updateAllCampaignStatus(currentOrgId, "PAUSED")
API->>Backend: PATCH /api/project/{orgId}/status?status=PAUSED
Backend-->>API: success
API-->>AdsListPage: void
AdsListPage->>AdsListPage: 로컬 campaigns 상태 동기화 / 토스트 표시
Estimated code review effort🎯 4 (Complex) | ⏱️ ~40 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.OpenGrep is compatible with Semgrep configurations. Add an |
📚 Storybook 배포 완료
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/pages/ads/list/AdsListPage.tsx (1)
107-167:⚠️ Potential issue | 🟠 Major재개 CTA를
hasActiveCampaign의 반대로만 결정하면 오동작합니다.캠페인이 하나도 없거나 전부
OVER인 경우에도 지금 분기에서는 바로 "시작하기" 박스가 노출됩니다. 이 경우 재개 대상이 없는데 잘못된 액션을 안내하게 되고, 조직이 없는 초기/에러 상태에서는 confirm이 조용히 no-op가 됩니다.ON_GOING과PAUSED를 각각 따로 계산해서, 실제로 재개 가능한 캠페인이 있을 때만 재개 CTA를 보여 주세요.수정 예시
- const hasActiveCampaign = campaigns.some((c) => c.status === "ON_GOING"); + const hasPausableCampaign = campaigns.some((c) => c.status === "ON_GOING"); + const hasResumableCampaign = campaigns.some((c) => c.status === "PAUSED"); ... - {hasActiveCampaign ? ( + {currentOrgId !== null && hasPausableCampaign ? ( <ControlBox title="전체 캠페인을 완전히 중단할 수 있어요" description="모든 광고 노출이 즉시 멈추고, 연결된 플랫폼에서도 더 이상 광고가 집행되지 않아요." buttonText="중단하기" onButtonClick={() => setStopAllOpen(true)} buttonDisabled={isStopping} containerClassName="bg-status-red/7 border-status-red px-6 py-4 min-w-[650px] shrink-0" titleClassName="text-status-red font-heading3" descriptionClassName="font-body2 text-text-sub" buttonSize="big" buttonClassName="font-body1 bg-status-red" /> - ) : ( + ) : currentOrgId !== null && hasResumableCampaign ? ( <ControlBox title="중단된 캠페인을 다시 시작할 수 있어요" description="중단되었던 모든 캠페인의 광고 노출이 즉시 재개되며, 다시 활성화됩니다." buttonText="시작하기" onButtonClick={() => setResumeOpen(true)} buttonDisabled={isResuming} containerClassName="bg-status-blue/7 border-status-blue px-6 py-4 min-w-[650px] shrink-0" titleClassName="text-status-blue font-heading3" descriptionClassName="font-body2 text-text-sub" buttonSize="big" buttonClassName="font-body1 bg-status-blue" /> - )} + ) : null}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/ads/list/AdsListPage.tsx` around lines 107 - 167, The current UI decides between "중단하기" and "시작하기" solely on hasActiveCampaign, which shows a "시작하기" CTA even when there are no PAUSED campaigns to resume; compute a separate flag (e.g., const hasPausedCampaign = campaigns.some(c => c.status === "PAUSED")) and change the render logic so: if hasActiveCampaign show the stop ControlBox (uses setStopAllOpen, isStopping), else if hasPausedCampaign show the resume ControlBox (uses setResumeOpen, isResuming), otherwise render nothing or a neutral disabled box—update references to campaigns, hasActiveCampaign, hasPausedCampaign, setResumeOpen, setStopAllOpen, isResuming, isStopping, and ControlBox accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/components/ads/CampaignRow.tsx`:
- Around line 26-33: The component CampaignRow currently destructures projectId
from props but never uses it, causing TS6133; remove projectId from the
destructuring list in the CampaignRow function signature while leaving projectId
in the ICampaignRowProps interface (so callers still provide it), i.e., stop
extracting projectId in the CampaignRow parameter list to eliminate the unused
variable error.
In `@src/components/ads/CampaignTable.tsx`:
- Around line 31-44: Create a filtered list (e.g., const visibleCampaigns =
campaigns?.filter(c => c.status !== "OVER") ?? []) and use
visibleCampaigns.length for the conditional render instead of campaigns.length;
map visibleCampaigns to render <CampaignRow key={projectId} {...project}
onClick={() => onRowClick?.(project.projectId)} /> and render the empty state as
an <li> (not a <div>) so it remains a direct semantic child of the surrounding
<ul>, and ensure any necessary ARIA/semantic attributes are preserved on the
empty <li>.
In `@src/pages/ads/list/AdsListPage.tsx`:
- Around line 21-48: The initData useEffect currently handles API calls, loading
and error state and local cache (getMyWorkspaces -> getCampaignList,
setCampaigns, setIsLoading, setCurrentOrgId) and should be refactored to React
Query: create custom hooks like useAdsCampaigns (which calls getMyWorkspaces
then getCampaignList and returns data/loading/error) and useUpdateCampaignStatus
for mutations, replace initData and its try/catch/setIsLoading logic with
useQuery hooks in AdsListPage, remove manual setCampaigns and instead read from
the query result, and use queryClient.invalidateQueries where needed to refresh
caches instead of manual state updates.
- Around line 17-48: The component declares isLoading/setIsLoading but never
reads it, causing TS6133 and showing the "Start" CTA while data is loading;
update the AdsListPage JSX to branch on isLoading (set by initData) so you
render a loading indicator (or skeleton) while isLoading is true, compute
hasActiveCampaign only after loading completes (use campaigns once isLoading is
false) and hide/disable the "시작하기" CTA until isLoading is false and
hasActiveCampaign is determined; ensure references to isLoading are used in the
render logic so the linter error is resolved.
In `@src/types/ads/campaign.ts`:
- Around line 5-18: The ICampaign/ICampaignDetail types don't match the mock
data and UI usage: update the type definitions or introduce a UI-specific
interface and align the mock typing. Specifically, either add the missing fields
(budget, startDate, statusText, progress, runStatus, runStatusText, ads) to
ICampaign/ICampaignDetail so CampaignDetail.tsx can safely read data.budget and
data.startDate, or create a new interface (e.g., ICampaignDetailWithUI) that
includes those UI-only fields and change MOCK_CAMPAIGNS' type to that interface
and use it in CampaignDetail.tsx; ensure references to ICampaign,
ICampaignDetail, MOCK_CAMPAIGNS, and the data.budget/data.startDate reads are
updated accordingly.
---
Outside diff comments:
In `@src/pages/ads/list/AdsListPage.tsx`:
- Around line 107-167: The current UI decides between "중단하기" and "시작하기" solely
on hasActiveCampaign, which shows a "시작하기" CTA even when there are no PAUSED
campaigns to resume; compute a separate flag (e.g., const hasPausedCampaign =
campaigns.some(c => c.status === "PAUSED")) and change the render logic so: if
hasActiveCampaign show the stop ControlBox (uses setStopAllOpen, isStopping),
else if hasPausedCampaign show the resume ControlBox (uses setResumeOpen,
isResuming), otherwise render nothing or a neutral disabled box—update
references to campaigns, hasActiveCampaign, hasPausedCampaign, setResumeOpen,
setStopAllOpen, isResuming, isStopping, and ControlBox accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 64bef2b0-302a-44c5-84fb-d98886c53bdc
📒 Files selected for processing (6)
src/api/ads/ads.tssrc/api/common/common.tssrc/components/ads/CampaignRow.tsxsrc/components/ads/CampaignTable.tsxsrc/pages/ads/list/AdsListPage.tsxsrc/types/ads/campaign.ts
📚 Storybook 배포 완료
|
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/pages/ads/list/CampaignDetail.tsx (1)
77-85:⚠️ Potential issue | 🟠 Major플랫폼 카드가 실제 연결 플랫폼을 반영하지 않습니다.
상세 타입에
providers를 올려 놓았는데 여기서는 여전히 3개 플랫폼을 하드코딩하고 있어서, 일부 플랫폼만 연결된 캠페인도 모두 연결된 것처럼 보입니다.data.providers를 그대로 넘겨야 상세 화면과 목록 화면이 일치합니다.수정 예시
<PlatformCard - platforms={["kakao", "google", "naver"]} + platforms={data.providers} className="flex-1 min-w-[320px] w-full" />🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/ads/list/CampaignDetail.tsx` around lines 77 - 85, The PlatformCard is being fed a hardcoded array ["kakao","google","naver"] which makes every campaign look fully connected; update the CampaignDetail component to pass the actual providers from the campaign data (use data.providers) into PlatformCard instead of the hardcoded list, and if necessary adapt or map data.providers to the exact prop shape PlatformCard expects so the detail view reflects the real connected platforms.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/components/ads/CampaignRow.tsx`:
- Around line 11-18: The component props declare onClick as optional in
ICampaignRowProps but the rendered row always gets role="button", keyboard
handlers, and hover cursor; update the component so it either (A) makes onClick
required in ICampaignRowProps and ensure all usages pass it, or (B) keep onClick
optional but conditionally add role="button", tabIndex, keyDown/keyboard
handlers, and hover cursor styles only when onClick is provided (i.e., check the
onClick prop before attaching interactive attributes/handlers in CampaignRow);
adjust any places that use CampaignRow accordingly to satisfy the chosen
approach.
In `@src/pages/ads/list/CampaignDetail.tsx`:
- Around line 21-22: 주석 처리된 상태 분기(isPaused, isOngoing)를 복원하고 data.status에 따라 하단
제어 박스의 버튼 문구·스타일·클릭 핸들러를 분기하세요: data.status === "PAUSED"일 때는 버튼을 "재개"로 표시하고
resumeOpen 모달을 여는 재개 핸들러를 연결하며, data.status === "ON_GOING"일 때는 버튼을 "중단하기"로 표시하고
중단 핸들러(pause 처리)를 연결하도록 CampaignDetail 컴포넌트의 해당 렌더링 로직과 클릭 이벤트를 수정하세요; 기타 상태는
기본/비활성 스타일로 처리해 UI와 동작이 일치하도록 만드세요.
- Line 4: Remove the unnecessary type assertion "as ICampaignDetail" and use the
actual MOCK_CAMPAIGNS-typed data; replace the hardcoded platforms array passed
to the CampaignDetail component (platforms={["kakao","google","naver"]}) with
the real provider list from the campaign data (platforms={data.providers}) so
each campaign renders its correct platforms, and implement the commented
isPaused/isOngoing checks (complete the logic where isPaused/isOngoing are
referenced) so the component derives pause/ongoing state from the campaign
object rather than leaving those lines commented out.
---
Outside diff comments:
In `@src/pages/ads/list/CampaignDetail.tsx`:
- Around line 77-85: The PlatformCard is being fed a hardcoded array
["kakao","google","naver"] which makes every campaign look fully connected;
update the CampaignDetail component to pass the actual providers from the
campaign data (use data.providers) into PlatformCard instead of the hardcoded
list, and if necessary adapt or map data.providers to the exact prop shape
PlatformCard expects so the detail view reflects the real connected platforms.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d01f9e79-c4e8-40b0-be61-ea010d475bb7
📒 Files selected for processing (5)
src/components/ads/CampaignRow.tsxsrc/pages/ads/list/AdsListPage.tsxsrc/pages/ads/list/CampaignDetail.tsxsrc/pages/ads/list/campaign.mock.tssrc/types/ads/campaign.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- src/pages/ads/list/AdsListPage.tsx
📚 Storybook 배포 완료
|
Collaborator
|
P4: 저도 종료상태인경우 해당 캠페인을 목록에 표시하지 않는 것이 지금으로써는 충분한것같습니다. 다만, 종료된 캠페인을 사용자가 확인하는 것을 원할 수 있기에, 추후에 한번 논의해보는 것이 좋을것같습니다! |
Seojegyeong
reviewed
Mar 16, 2026
Collaborator
|
P4: 저는 종료된 캠페인도 확인할 수 있도록 하는게 좋을 것 같습니다. 대면 회의 때 의논해보면 좋을 것 같습니다 :) 수고하셨습니다! |
📚 Storybook 배포 완료
|
There was a problem hiding this comment.
🧹 Nitpick comments (2)
src/pages/ads/list/AdsListPage.tsx (2)
134-137:onRowClick핸들러 인라인 함수 고려사항현재
onRowClick={(id) => handleCampaignClick(id)}는 매 렌더링마다 새 함수를 생성해요.CampaignTable이React.memo로 래핑되어 있다면 불필요한 리렌더링을 유발할 수 있습니다.간소화 제안
<CampaignTable campaigns={campaigns} - onRowClick={(id) => handleCampaignClick(id)} + onRowClick={handleCampaignClick} />
handleCampaignClick을 직접 전달하면 동일한 동작을 하면서 코드도 간결해집니다.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/ads/list/AdsListPage.tsx` around lines 134 - 137, The inline arrow for onRowClick creates a new function each render which can trigger unnecessary re-renders of CampaignTable; change the prop to pass handleCampaignClick directly (CampaignTable onRowClick={handleCampaignClick}) or, if needed, wrap handleCampaignClick in useCallback so its identity is stable; update the invocation sites to continue accepting the id parameter (i.e., ensure handleCampaignClick(id) signature remains unchanged).
66-105: 상태 업데이트 로직이 API 호출 성공 후에 실행되고 있어요.현재 구현은 API 호출 성공 후 로컬 상태를 업데이트하는 방식인데, 이는 올바른 접근입니다. 다만 몇 가지 개선점이 있습니다:
상태 문자열 타입 안전성:
"PAUSED","ON_GOING"문자열이 하드코딩되어 있어요.ICampaign의status타입과 일치하는지 확인이 필요합니다.에러 로깅 부재: catch 블록에서 에러 객체를 사용하지 않아 디버깅 시 원인 파악이 어려울 수 있어요.
개선 제안
- const onStopAll = async () => { + const onStopAll = async () => { if (!currentOrgId) return; setIsStopping(true); try { await updateAllCampaignStatus(currentOrgId, "PAUSED"); setCampaigns((prev) => prev.map((c) => c.status === "ON_GOING" ? { ...c, status: "PAUSED" } : c, ), ); toast.success("전체 캠페인의 모든 광고 노출이 중단되었습니다."); setStopAllOpen(false); - } catch { - toast.error("중단 처리에 실패하였습니다."); + } catch (error) { + console.error("캠페인 중단 실패:", error); + toast.error("중단 처리에 실패하였습니다."); } finally { setIsStopping(false); } };
onResumeAll에도 동일하게 적용해 주세요.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/ads/list/AdsListPage.tsx` around lines 66 - 105, The onStopAll and onResumeAll handlers use hardcoded status strings ("PAUSED", "ON_GOING") and swallow errors; update them to use your canonical status enum/type (e.g., ICampaignStatus or a STATUS constant used across the codebase) instead of raw strings to ensure type safety and consistency, and modify the catch blocks in both onStopAll and onResumeAll to accept and log the caught error (e.g., catch (err) { console.error(err); toast.error(...) }) so failures are recorded for debugging while keeping the existing toast messages and state updates with the enum/constant values (refer to functions onStopAll, onResumeAll and the updateAllCampaignStatus call to locate where to change the strings and add error logging).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@src/pages/ads/list/AdsListPage.tsx`:
- Around line 134-137: The inline arrow for onRowClick creates a new function
each render which can trigger unnecessary re-renders of CampaignTable; change
the prop to pass handleCampaignClick directly (CampaignTable
onRowClick={handleCampaignClick}) or, if needed, wrap handleCampaignClick in
useCallback so its identity is stable; update the invocation sites to continue
accepting the id parameter (i.e., ensure handleCampaignClick(id) signature
remains unchanged).
- Around line 66-105: The onStopAll and onResumeAll handlers use hardcoded
status strings ("PAUSED", "ON_GOING") and swallow errors; update them to use
your canonical status enum/type (e.g., ICampaignStatus or a STATUS constant used
across the codebase) instead of raw strings to ensure type safety and
consistency, and modify the catch blocks in both onStopAll and onResumeAll to
accept and log the caught error (e.g., catch (err) { console.error(err);
toast.error(...) }) so failures are recorded for debugging while keeping the
existing toast messages and state updates with the enum/constant values (refer
to functions onStopAll, onResumeAll and the updateAllCampaignStatus call to
locate where to change the strings and add error logging).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: ee367bce-3105-4af6-93c0-bef8097601ff
📒 Files selected for processing (2)
src/api/ads/ads.tssrc/pages/ads/list/AdsListPage.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
- src/api/ads/ads.ts
Seojegyeong
approved these changes
Mar 16, 2026
📚 Storybook 배포 완료
|
There was a problem hiding this comment.
♻️ Duplicate comments (1)
src/components/ads/CampaignRow.tsx (1)
36-43:⚠️ Potential issue | 🟡 Minor
onClick가 없을 때도 인터랙티브 행으로 노출됩니다.Line 17에서
onClick은 optional인데, Line 36/41/43에서 hover·cursor·role="button"·키보드 핸들러가 항상 적용됩니다.isInteractive = Boolean(onClick)로 조건부 적용하거나, 반대로onClick을 필수 prop으로 고정해 주세요.As per coding guidelines,
7. 접근성: 시맨틱 HTML, ARIA 속성 사용 확인.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/components/ads/CampaignRow.tsx` around lines 36 - 43, The row is being exposed as interactive even when onClick is optional; introduce a local flag like isInteractive = Boolean(onClick) in CampaignRow and use it to conditionally apply interactive behavior: only add role="button", tabIndex (e.g., 0), the onKeyDown keyboard handler, and the hover/cursor CSS classes when isInteractive is true (leave isPaused logic intact for background styling); update the className template to include hover:bg-bg-surface and hover:cursor-pointer only when isInteractive, and guard the onKeyDown and tabIndex props so non-interactive rows are not treated as buttons.
🧹 Nitpick comments (1)
src/components/ads/CampaignRow.tsx (1)
76-80: 주석 처리된 상태 배지 블록은 정리하는 게 좋습니다.비활성화된 JSX를 파일에 남겨두면 이후 유지보수 시 의도를 추적하기 어렵습니다. 재사용 계획이 없다면 삭제하고, 필요하면 PR 설명/이슈로 의도를 남기는 쪽이 더 깔끔합니다.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/components/ads/CampaignRow.tsx` around lines 76 - 80, Remove the commented-out JSX block that renders the status badge in CampaignRow.tsx (the disabled div containing Badge, status, and statusText); if you expect to reuse this UI later, instead create a short PR description or open an issue linking the intended reuse and remove the dead commented code from the file to keep the component clean and maintainable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@src/components/ads/CampaignRow.tsx`:
- Around line 36-43: The row is being exposed as interactive even when onClick
is optional; introduce a local flag like isInteractive = Boolean(onClick) in
CampaignRow and use it to conditionally apply interactive behavior: only add
role="button", tabIndex (e.g., 0), the onKeyDown keyboard handler, and the
hover/cursor CSS classes when isInteractive is true (leave isPaused logic intact
for background styling); update the className template to include
hover:bg-bg-surface and hover:cursor-pointer only when isInteractive, and guard
the onKeyDown and tabIndex props so non-interactive rows are not treated as
buttons.
---
Nitpick comments:
In `@src/components/ads/CampaignRow.tsx`:
- Around line 76-80: Remove the commented-out JSX block that renders the status
badge in CampaignRow.tsx (the disabled div containing Badge, status, and
statusText); if you expect to reuse this UI later, instead create a short PR
description or open an issue linking the intended reuse and remove the dead
commented code from the file to keep the component clean and maintainable.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 71c933ae-26db-4095-b512-87f2defe2ee9
📒 Files selected for processing (2)
src/components/ads/CampaignRow.tsxsrc/components/ads/CampaignTable.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
- src/components/ads/CampaignTable.tsx
Seojegyeong
approved these changes
Mar 16, 2026
jjjsun
approved these changes
Mar 16, 2026
📚 Storybook 배포 완료
|
Seojegyeong
approved these changes
Mar 17, 2026
This was referenced Mar 18, 2026
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 관련 이슈
close #95
✨ 변경사항
✏️ 작업 내용
서버 응답에 따른 인터페이스 수정
캠페인 목록 조회 API 연동
/api/project/{orgId}캠페인 운영 상태별 UI 처리
OVER(종료) : 목록에서 제외 필터링 로직 추가PAUSED(중단) : 해당 캠페인의 Row 배경색/텍스트 회색 처리전체 캠페인 통합 제어 기능
/api/project/{orgId}/statusAPI 연동 (중단/재개)😅 미완성 작업
N/A
📢 논의 사항 및 참고 사항
Summary by CodeRabbit
릴리스 노트
새 기능
개선