@lumeweb/pinner 0.1.13 → 0.1.14

package/dist/esm/api/generated/schemas/websiteConfigResponse.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/websiteConfigResponse.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface WebsiteConfigResponse {

package/dist/esm/api/generated/schemas/websiteRequest.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/websiteRequest.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface WebsiteRequest {

package/dist/esm/api/generated/schemas/websiteUpdateRequest.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/websiteUpdateRequest.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface WebsiteUpdateRequest {

package/dist/esm/api/generated/schemas/websiteValidateResponse.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/websiteValidateResponse.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface WebsiteValidateResponse {

package/dist/esm/api/generated/schemas/zoneListResponse.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/zoneListResponse.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface ZoneListResponse {

package/dist/esm/api/generated/schemas/zoneResponse.d.ts

@@ -1,37 +1,37 @@
 //#region src/api/generated/schemas/zoneResponse.d.ts
 /**
- * Generated by orval v8.10.0 🍺
+ * Generated by orval v8.18.0 🍺
  * Do not edit manually.
  * Portal IPFS Plugin API
  *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+ * ## Portal IPFS Plugin API
+ *
+ * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+ *
+ * ### IPFS Pinning Service API Compatibility
+ *
+ * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+ *
+ * ### Features
+ *
+ * - **Pinning**: Add, list, update, and remove pinned content
+ * - **Content**: Upload files, retrieve IPFS content, and manage metadata
+ * - **IPNS**: Manage IPNS keys and publish content
+ * - **Files**: Browse and manage pinned files with directory navigation
+ * - **Websites**: Create and manage website hosting with DNS and SSL automation
+ *
+ * ### Authentication
+ *
+ * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+ *
+ * ### Rate Limiting
+ *
+ * API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+ *
+ * ### Documentation
+ *
+ * For detailed API usage examples and integration guides, visit the Portal documentation website.
+ *
  * OpenAPI spec version: 1.0.0
  */
 interface ZoneResponse {

package/dist/esm/api/generated/tus/tus.msw.js

@@ -1,40 +1,40 @@
 import { faker } from "@faker-js/faker";
-import { HttpResponse, delay, http } from "msw";
+import { HttpResponse, http } from "msw";
 
 //#region src/api/generated/tus/tus.msw.ts
 /**
-* Generated by orval v8.10.0 🍺
+* Generated by orval v8.18.0 🍺
 * Do not edit manually.
 * Portal IPFS Plugin API
 *
-## Portal IPFS Plugin API
-
-A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
-
-### IPFS Pinning Service API Compatibility
-
-This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
-
-### Features
-
-- **Pinning**: Add, list, update, and remove pinned content
-- **Content**: Upload files, retrieve IPFS content, and manage metadata
-- **IPNS**: Manage IPNS keys and publish content
-- **Files**: Browse and manage pinned files with directory navigation
-- **Websites**: Create and manage website hosting with DNS and SSL automation
-
-### Authentication
-
-All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
-
-### Rate Limiting
-
-API requests are rate-limited based on user account tier. See Portal documentation for current limits.
-
-### Documentation
-
-For detailed API usage examples and integration guides, visit the Portal documentation website.
-
+* ## Portal IPFS Plugin API
+*
+* A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.
+*
+* ### IPFS Pinning Service API Compatibility
+*
+* This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.
+*
+* ### Features
+*
+* - **Pinning**: Add, list, update, and remove pinned content
+* - **Content**: Upload files, retrieve IPFS content, and manage metadata
+* - **IPNS**: Manage IPNS keys and publish content
+* - **Files**: Browse and manage pinned files with directory navigation
+* - **Websites**: Create and manage website hosting with DNS and SSL automation
+*
+* ### Authentication
+*
+* All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.
+*
+* ### Rate Limiting
+*
+* API requests are rate-limited based on user account tier. See Portal documentation for current limits.
+*
+* ### Documentation
+*
+* For detailed API usage examples and integration guides, visit the Portal documentation website.
+*
 * OpenAPI spec version: 1.0.0
 */
 const getPostApiUploadTusResponseMock = (overrideResponse = {}) => ({
@@ -60,28 +60,24 @@ const getPatchApiUploadTusIdResponseMock = (overrideResponse = {}) => ({
 });
 const getPostApiUploadTusMockHandler = (overrideResponse, options) => {
 	return http.post("*/api/upload/tus", async (info) => {
-		await delay(0);
 		const resolvedBody = overrideResponse !== void 0 ? typeof overrideResponse === "function" ? await overrideResponse(info) : overrideResponse : getPostApiUploadTusResponseMock();
 		return resolvedBody === void 0 ? new HttpResponse(null, { status: 201 }) : HttpResponse.json(resolvedBody, { status: 200 });
 	}, options);
 };
 const getDeleteApiUploadTusIdMockHandler = (overrideResponse, options) => {
 	return http.delete("*/api/upload/tus/:id", async (info) => {
-		await delay(0);
 		const resolvedBody = overrideResponse !== void 0 ? typeof overrideResponse === "function" ? await overrideResponse(info) : overrideResponse : getDeleteApiUploadTusIdResponseMock();
 		return resolvedBody === void 0 ? new HttpResponse(null, { status: 204 }) : HttpResponse.json(resolvedBody, { status: 200 });
 	}, options);
 };
 const getHeadApiUploadTusIdMockHandler = (overrideResponse, options) => {
 	return http.head("*/api/upload/tus/:id", async (info) => {
-		await delay(0);
 		if (typeof overrideResponse === "function") await overrideResponse(info);
 		return new HttpResponse(null, { status: 200 });
 	}, options);
 };
 const getPatchApiUploadTusIdMockHandler = (overrideResponse, options) => {
 	return http.patch("*/api/upload/tus/:id", async (info) => {
-		await delay(0);
 		const resolvedBody = overrideResponse !== void 0 ? typeof overrideResponse === "function" ? await overrideResponse(info) : overrideResponse : getPatchApiUploadTusIdResponseMock();
 		return resolvedBody === void 0 ? new HttpResponse(null, { status: 204 }) : HttpResponse.json(resolvedBody, { status: 200 });
 	}, options);

package/dist/esm/api/generated/tus/tus.msw.js.map

@@ -1 +1 @@
-{"version":3,"file":"tus.msw.js","names":[],"sources":["../../../../../src/api/generated/tus/tus.msw.ts"],"sourcesContent":["/**\n * Generated by orval v8.10.0 🍺\n * Do not edit manually.\n * Portal IPFS Plugin API\n *\n## Portal IPFS Plugin API\n\nA comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.\n\n### IPFS Pinning Service API Compatibility\n\nThis API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.\n\n### Features\n\n- **Pinning**: Add, list, update, and remove pinned content\n- **Content**: Upload files, retrieve IPFS content, and manage metadata\n- **IPNS**: Manage IPNS keys and publish content\n- **Files**: Browse and manage pinned files with directory navigation\n- **Websites**: Create and manage website hosting with DNS and SSL automation\n\n### Authentication\n\nAll API endpoints require authentication using JWT tokens obtained from the Portal authentication service.\n\n### Rate Limiting\n\nAPI requests are rate-limited based on user account tier. See Portal documentation for current limits.\n\n### Documentation\n\nFor detailed API usage examples and integration guides, visit the Portal documentation website.\n\n * OpenAPI spec version: 1.0.0\n */\nimport {\n  faker\n} from '@faker-js/faker';\n\nimport {\n  HttpResponse,\n  delay,\n  http\n} from 'msw';\nimport type {\n  RequestHandlerOptions\n} from 'msw';\n\nimport type {\n  ErrorResponse\n} from '../schemas';\n\n\nexport const getPostApiUploadTusResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\nexport const getDeleteApiUploadTusIdResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\nexport const getPatchApiUploadTusIdResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\n\nexport const getPostApiUploadTusMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.post>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.post('*/api/upload/tus', async (info: Parameters<Parameters<typeof http.post>[1]>[0]) => {await delay(0);\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getPostApiUploadTusResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 201 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\n\nexport const getDeleteApiUploadTusIdMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.delete>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.delete('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.delete>[1]>[0]) => {await delay(0);\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getDeleteApiUploadTusIdResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 204 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\n\nexport const getHeadApiUploadTusIdMockHandler = (overrideResponse?: void | ((info: Parameters<Parameters<typeof http.head>[1]>[0]) => Promise<void> | void), options?: RequestHandlerOptions) => {\n  return http.head('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.head>[1]>[0]) => {await delay(0);\n  if (typeof overrideResponse === 'function') {await overrideResponse(info); }\n\n    return new HttpResponse(null,\n      { status: 200\n      })\n  }, options)\n}\n\nexport const getPatchApiUploadTusIdMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.patch>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.patch('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.patch>[1]>[0]) => {await delay(0);\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getPatchApiUploadTusIdResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 204 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\nexport const getTusMock = () => [\n  getPostApiUploadTusMockHandler(),\n  getDeleteApiUploadTusIdMockHandler(),\n  getHeadApiUploadTusIdMockHandler(),\n  getPatchApiUploadTusIdMockHandler()\n]\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAqDA,MAAa,mCAAmC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAEjN,MAAa,uCAAuC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAErN,MAAa,sCAAsC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAGpN,MAAa,kCAAkC,kBAA4J,YAAoC;AAC7O,QAAO,KAAK,KAAK,oBAAoB,OAAO,SAAyD;AAAC,QAAM,MAAM,EAAE;EAEpH,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,iCAAiC;AACnC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAGb,MAAa,sCAAsC,kBAA8J,YAAoC;AACnP,QAAO,KAAK,OAAO,wBAAwB,OAAO,SAA2D;AAAC,QAAM,MAAM,EAAE;EAE5H,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,qCAAqC;AACvC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAGb,MAAa,oCAAoC,kBAA4G,YAAoC;AAC/L,QAAO,KAAK,KAAK,wBAAwB,OAAO,SAAyD;AAAC,QAAM,MAAM,EAAE;AACxH,MAAI,OAAO,qBAAqB,WAAa,OAAM,iBAAiB,KAAK;AAEvE,SAAO,IAAI,aAAa,MACtB,EAAE,QAAQ,KACT,CAAC;IACH,QAAQ;;AAGb,MAAa,qCAAqC,kBAA6J,YAAoC;AACjP,QAAO,KAAK,MAAM,wBAAwB,OAAO,SAA0D;AAAC,QAAM,MAAM,EAAE;EAE1H,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,oCAAoC;AACtC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAEb,MAAa,mBAAmB;CAC9B,gCAAgC;CAChC,oCAAoC;CACpC,kCAAkC;CAClC,mCAAmC;CACpC"}
+{"version":3,"file":"tus.msw.js","names":[],"sources":["../../../../../src/api/generated/tus/tus.msw.ts"],"sourcesContent":["/**\n * Generated by orval v8.18.0 🍺\n * Do not edit manually.\n * Portal IPFS Plugin API\n *\n * ## Portal IPFS Plugin API\n *\n * A comprehensive API for IPFS content management, including pinning services, file operations, IPNS key management, and website hosting.\n *\n * ### IPFS Pinning Service API Compatibility\n *\n * This API is fully compatible with the [IPFS Pinning Service API specification](https://github.com/ipfs/pinning-services-api-spec), an implementation-agnostic API standard for pinning service providers. This ensures interoperability with existing IPFS pinning clients and tools.\n *\n * ### Features\n *\n * - **Pinning**: Add, list, update, and remove pinned content\n * - **Content**: Upload files, retrieve IPFS content, and manage metadata\n * - **IPNS**: Manage IPNS keys and publish content\n * - **Files**: Browse and manage pinned files with directory navigation\n * - **Websites**: Create and manage website hosting with DNS and SSL automation\n *\n * ### Authentication\n *\n * All API endpoints require authentication using JWT tokens obtained from the Portal authentication service.\n *\n * ### Rate Limiting\n *\n * API requests are rate-limited based on user account tier. See Portal documentation for current limits.\n *\n * ### Documentation\n *\n * For detailed API usage examples and integration guides, visit the Portal documentation website.\n *\n * OpenAPI spec version: 1.0.0\n */\nimport {\n  faker\n} from '@faker-js/faker';\n\nimport {\n  HttpResponse,\n  http\n} from 'msw';\nimport type {\n  RequestHandlerOptions\n} from 'msw';\n\nimport type {\n  ErrorResponse\n} from '../schemas';\n\n\nexport const getPostApiUploadTusResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\nexport const getDeleteApiUploadTusIdResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\nexport const getPatchApiUploadTusIdResponseMock = (overrideResponse: Partial<Extract<ErrorResponse, object>> = {}): ErrorResponse => ({error: faker.string.alpha({length: {min: 10, max: 20}}), ...overrideResponse})\n\n\nexport const getPostApiUploadTusMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.post>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.post('*/api/upload/tus', async (info: Parameters<Parameters<typeof http.post>[1]>[0]) => {\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getPostApiUploadTusResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 201 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\n\nexport const getDeleteApiUploadTusIdMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.delete>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.delete('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.delete>[1]>[0]) => {\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getDeleteApiUploadTusIdResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 204 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\n\nexport const getHeadApiUploadTusIdMockHandler = (overrideResponse?: void | ((info: Parameters<Parameters<typeof http.head>[1]>[0]) => Promise<void> | void), options?: RequestHandlerOptions) => {\n  return http.head('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.head>[1]>[0]) => {\n  if (typeof overrideResponse === 'function') {await overrideResponse(info); }\n\n    return new HttpResponse(null,\n      { status: 200\n      })\n  }, options)\n}\n\nexport const getPatchApiUploadTusIdMockHandler = (overrideResponse?: ErrorResponse | void | ((info: Parameters<Parameters<typeof http.patch>[1]>[0]) => Promise<ErrorResponse | void> | ErrorResponse | void), options?: RequestHandlerOptions) => {\n  return http.patch('*/api/upload/tus/:id', async (info: Parameters<Parameters<typeof http.patch>[1]>[0]) => {\n\n  const resolvedBody = overrideResponse !== undefined\n    ? (typeof overrideResponse === \"function\" ? await overrideResponse(info) : overrideResponse)\n    : getPatchApiUploadTusIdResponseMock();\n    return resolvedBody === undefined\n      ? new HttpResponse(null, { status: 204 })\n      : HttpResponse.json(resolvedBody, { status: 200 })\n  }, options)\n}\nexport const getTusMock = () => [\n  getPostApiUploadTusMockHandler(),\n  getDeleteApiUploadTusIdMockHandler(),\n  getHeadApiUploadTusIdMockHandler(),\n  getPatchApiUploadTusIdMockHandler()\n]\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAoDA,MAAa,mCAAmC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAEjN,MAAa,uCAAuC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAErN,MAAa,sCAAsC,mBAA4D,EAAE,MAAqB;CAAC,OAAO,MAAM,OAAO,MAAM,EAAC,QAAQ;EAAC,KAAK;EAAI,KAAK;EAAG,EAAC,CAAC;CAAE,GAAG;CAAiB;AAGpN,MAAa,kCAAkC,kBAA4J,YAAoC;AAC7O,QAAO,KAAK,KAAK,oBAAoB,OAAO,SAAyD;EAErG,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,iCAAiC;AACnC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAGb,MAAa,sCAAsC,kBAA8J,YAAoC;AACnP,QAAO,KAAK,OAAO,wBAAwB,OAAO,SAA2D;EAE7G,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,qCAAqC;AACvC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAGb,MAAa,oCAAoC,kBAA4G,YAAoC;AAC/L,QAAO,KAAK,KAAK,wBAAwB,OAAO,SAAyD;AACzG,MAAI,OAAO,qBAAqB,WAAa,OAAM,iBAAiB,KAAK;AAEvE,SAAO,IAAI,aAAa,MACtB,EAAE,QAAQ,KACT,CAAC;IACH,QAAQ;;AAGb,MAAa,qCAAqC,kBAA6J,YAAoC;AACjP,QAAO,KAAK,MAAM,wBAAwB,OAAO,SAA0D;EAE3G,MAAM,eAAe,qBAAqB,SACrC,OAAO,qBAAqB,aAAa,MAAM,iBAAiB,KAAK,GAAG,mBACzE,oCAAoC;AACtC,SAAO,iBAAiB,SACpB,IAAI,aAAa,MAAM,EAAE,QAAQ,KAAK,CAAC,GACvC,aAAa,KAAK,cAAc,EAAE,QAAQ,KAAK,CAAC;IACnD,QAAQ;;AAEb,MAAa,mBAAmB;CAC9B,gCAAgC;CAChC,oCAAoC;CACpC,kCAAkC;CAClC,mCAAmC;CACpC"}