Refactor data communication layer with improved token management

[Copilot]

The axios configuration had token initialization timing issues and lacked proper refresh token validation, causing potential authentication failures.

Changes

src/api/axios.js

• Moved token retrieval from instance creation to request interceptor (fixes stale token on initialization)
• Added null check for refresh token before attempting reissue
• Used base axios for token refresh to prevent interceptor recursion
• Removed commented code blocks

New: src/api/apiService.js

• Abstraction layer for HTTP operations (GET, POST, PUT, PATCH, DELETE, upload)
• Consistent response unwrapping (response.data)
• JSDoc annotations

New: src/api/index.js

• Central export point for axios utilities

New: src/api/README.md

• Usage examples and module documentation (Korean)

Example Usage

Before:

import axiosInstance from '../api/axios';
const response = await axiosInstance.get('/trip/1');
const data = response.data;  // Manual unwrapping

After (optional convenience layer):

import { apiService } from '../api';
const data = await apiService.get('/trip/1');  // Auto-unwrapped

All existing axiosInstance usage continues to work without modification.

Original prompt

데이터 통신

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dodutch	Error			Nov 10, 2025 5:18am