arky-sdk 0.7.118 → 0.7.119

package/README.md

@@ -342,7 +342,7 @@ await arky.utils.injectSvgIntoElement(mediaBlock, element, 'custom-class')
 
 - 🏪 **E-commerce shops** - Product catalogs, shopping carts, checkout
 - 📰 **Content websites** - Blogs, documentation, marketing sites
-- 📅 **Booking platforms** - Appointment scheduling, service bookings
+- 📅 **Service businesses** - Appointment scheduling, service orders
 - 📬 **Newsletter platforms** - Subscriber management, email campaigns
 - 🏢 **SaaS products** - Multi-tenant apps with user auth and billing
 - 🛍️ **Marketplaces** - Multi-vendor platforms with payments
@@ -393,7 +393,7 @@ When adding a new SDK method, follow this checklist so the API surface stays typ
 2. **Define the request params** in `src/types/api.ts`. Mirror the Rust DTO in `server/core/src/{module}/types/commands.rs` field-for-field. Two exceptions: `store_id?: string` and `market?: string` are optional in TS (the SDK auto-fills both from `apiConfig.storeId` and `apiConfig.market`). Do **not** use `[key: string]: any` index signatures.
 3. **Annotate the SDK method's return type** using the matching entity from `src/types/index.ts`.
 4. **Pass the response generic to the HTTP call**: `apiConfig.httpClient.post<EntityType>(...)`, `apiConfig.httpClient.get<PaginatedResponse<EntityType>>(...)`, etc. Never rely on inference.
-5. **Inject `market` from `apiConfig`**: when a body needs a `market` field, write `{ market: apiConfig.market, ...payload }`. Never hardcode `"booking"`, `"eshop"`, or any other market string in `src/api/*.ts`.
+5. **Inject `market` from `apiConfig`**: when a body needs a `market` field, write `{ market: apiConfig.market, ...payload }`. Never hardcode `"default"`, `"eshop"`, or any other market string in `src/api/*.ts`.
 6. **Re-export the entity** from `src/index.ts` if consumers (admin, storefront) will import it.
 7. **Bump `SDK_VERSION`** in `src/index.ts` and the `version` in `package.json`. Patch only.