@iyulab/enterprise 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.10.1
+
+### Added
+
+- **`ODataService` gained `apiPut<T>(path, body?)`.** The other three custom-REST verbs
+  (`apiGet`/`apiPost`/`apiPatch`/`apiDelete`) were already there; `PUT` was the one missing member
+  of that set, even though the underlying `@iyulab/http-client` `HttpClient` has always had `.put()`.
+  A consumer whose backend models "replace this resource" as `PUT` had no way to reach it through
+  this wrapper. Passing a `FormData` body to `apiPost`/`apiPut`/`apiPatch` already worked before this
+  change and needed no fix — `HttpClient` never forces JSON serialization on it and lets the browser
+  set the multipart boundary itself.
+
 ## 0.10.0
 
 ### Changed

package/README.md

@@ -95,9 +95,21 @@ export const svc = createODataService({
 
 await svc.odataGet<Order>('Orders', { $top: '20' })   // value 배열 언랩
 await svc.odataPost<Order>('Orders', { name: 'A', note: '' })  // '' → null 정규화 + 성공 토스트
-await svc.apiDelete('orders/7')                        // 204 안전
 svc.odataUrl('Orders')                                 // flex-table useODataSource 엔드포인트
 svc.sourceDefaults                                     // { baseUrl, onUnauthorized } 주입용
+
+// custom REST — GET/POST/PUT/PATCH/DELETE 전부, 204 빈 바디 안전 파싱 포함
+await svc.apiGet<Order>('reports/summary')
+await svc.apiPost<Order>('orders', { name: 'A' })
+await svc.apiPut<Order>('orders/7', { name: 'A (revised)' })    // 리소스 전체 교체
+await svc.apiPatch<Order>('orders/7', { note: 'urgent' })
+await svc.apiDelete('orders/7')                                 // 204 안전
+
+// body가 FormData 인스턴스면 그대로(직렬화 없이) 멀티파트로 전송된다 —
+// Content-Type은 브라우저가 boundary와 함께 자동 설정한다. apiPost/apiPut/apiPatch 전부 동일.
+const form = new FormData()
+form.append('file', file)
+await svc.apiPost<Order>('orders/7/attachments', form)
 ```
 
 주입 항목:

package/dist/data/ODataService.d.ts

@@ -73,9 +73,13 @@ export interface ODataService {
     odataDelete(entity: string, id: string): Promise<void>;
     /** custom REST GET — 204 등 빈 바디를 안전 파싱. */
     apiGet<T>(path: string): Promise<T>;
-    /** custom REST POST. */
+    /** custom REST POST. `body`가 `FormData` 인스턴스면 그대로(직렬화 없이) 멀티파트로
+     *  전송된다 — `@iyulab/http-client`가 Content-Type을 브라우저 자동 설정에 맡기고
+     *  JSON 직렬화 분기를 타지 않는다. `apiPut`/`apiPatch`도 동일하게 동작한다. */
     apiPost<T>(path: string, body?: unknown): Promise<T>;
-    /** custom REST PATCH. */
+    /** custom REST PUT(리소스 전체 교체/생성). `body`의 `FormData` 처리는 `apiPost` 참조. */
+    apiPut<T>(path: string, body?: unknown): Promise<T>;
+    /** custom REST PATCH. `body`의 `FormData` 처리는 `apiPost` 참조. */
     apiPatch<T>(path: string, body?: unknown): Promise<T>;
     /** custom REST DELETE — 대부분 204 No Content. */
     apiDelete<T = void>(path: string): Promise<T>;

package/dist/index.js

@@ -774,6 +774,11 @@ function createODataService(config) {
 		await throwIfError(res);
 		return parseJsonBody(res);
 	}
+	async function apiPut(path, body) {
+		const res = await client.put(apiUrl(path), body ?? {});
+		await throwIfError(res);
+		return parseJsonBody(res);
+	}
 	async function apiPatch(path, body) {
 		const res = await client.patch(apiUrl(path), body ?? {});
 		await throwIfError(res);
@@ -801,6 +806,7 @@ function createODataService(config) {
 		odataDelete,
 		apiGet,
 		apiPost,
+		apiPut,
 		apiPatch,
 		apiDelete,
 		fetchRaw,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iyulab/enterprise",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "Enterprise utilities and components for iyulab framework",
   "keywords": [
     "enterprise",