Skip to content

Add default multipart json fetch client#11

Open
vincentdbs wants to merge 1 commit intomasterfrom
feature/add-json-multipart-client
Open

Add default multipart json fetch client#11
vincentdbs wants to merge 1 commit intomasterfrom
feature/add-json-multipart-client

Conversation

@vincentdbs
Copy link
Copy Markdown
Collaborator

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • What is the current behavior? (You can also link to an open issue here)

  • What is the new behavior (if this is a feature change)?

  • Other information:

@vincentdbs vincentdbs requested a review from lucas-amiaud April 7, 2026 07:28
@vincentdbs vincentdbs force-pushed the feature/add-json-multipart-client branch from e0a6f9b to 1b5ff91 Compare April 7, 2026 08:23
*/
export const jsonContentTypeValidator: FetchResponseHandler = (
response: Response,
) => validateContentType(response, 'json'); No newline at end of file
Copy link
Copy Markdown
Member

@lucas-amiaud lucas-amiaud Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

je sais que c'était fait comme ca avant, mais c'est pas application/json ?

// ...
multipartRequest<T>(method: HttpMethod, path: string): MultipartHttpRequest<HttpPromise<T>> {
return createMultipartHttpFetchRequest<T>(baseUrl, method, path, multipartHttpFetchClient);
return createMultipartHttpFetchRequest<T>(baseUrl, method, path, defaultJsonMultipartFetchClient);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pour le coup je pousserais pas ce client par défaut dans le readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants