GitHub - Zellwk/zl-fetch: a Library that makes the Fetch API a Breeze > 자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

Use the response straight away without utilizing response.json(), response.text(), or response.blob(). Promise-like error handling - all 400 and 500 errors are directed into the catch block mechanically. Easy error handling when utilizing await - errors will be returned so you don't have to jot down a strive/catch block. Content-Type headers are set automatically based on the physique content material. Get every part you need about your response - headers, body, standing, and extra. Helper for generating query strings so you don't should mess with question parameters. Generates authorization headers with an auth property. Create situations to carry url and options so you don't must repeat your self. Note: zlFetch is a ESM library since v4.0.0. Then you need to use it by importing it in your JavaScript file. You may import zlFetch instantly into JavaScript through a CDN. To do this, you first have to set your script's sort to module, then import zlFetch. You need to use zlFetch similar to a traditional fetch function.

The only distinction is you don't have to write a response.json or response.textual content technique anymore! Fetch handles it for you automatically so you possibly can go straight to using your response. Fetch contains shorthand strategies for these frequent Rest methods so you should use them shortly. Fetch helps json, textual content, and blob response sorts so you do not have to write response.json(), response.text() or response.blob(). It also supports streams. See streaming for a better understanding of how this works. Other response varieties usually are not supported right now. Fetch sends you all the data you need within the response object. We do that so you don't must fish out the headers, status, statusText and even the remainder of the response object by your self. New in v4.0.0: You possibly can debug the request object by adding a debug choice. It will reveal a debug object that comprises the request being constructed. Fetch directs all four hundred and 500 errors to the catch technique.

Errors comprise the identical data as a response. This makes is zlFetch super straightforward to use with guarantees. Fetch helps you to go all errors into an errors object. You can do this by including a returnError option. This is beneficial when you work rather a lot with async/await. Fetch helps streaming in v6.2.0. It detects streams once you pass in stream: true as an option. It additionally gives a readable stream helper to decode the stream. The decoded stream is saved inside response.body so you possibly can simply loop by it to get your chunks. Below are a number of caveats you must know because the implementation modifications slightly due depending on how servers implement streaming. Fetch decodes the request body for you automatically for server-sent occasions. Just loop by means of the request.body to get your chunks. The pure zlFetch operate won't be one of the best at handling SSE as a result of it does not reconnect routinely when the connection is misplaced. See Streaming with Event Source for a recommended approach.

The Transfer-Encoding header does not reach the browser the stream is not going to be decoded robotically. To decode it within the browser, use the readStream helper we supplied. No need for this further step if you're sending the Fetch request from a server. Fetch detects it's a stream if there is no Content-Length header. For these streams, the Transfer-Encoding: chunked guidelines above apply. You possibly can abort a request - both regular Abusive Relationships and Domestic Violence streams - using the identical abort() method. We've added the abort operate to the .then name so you may call it while handling the response. If you happen to wish to, you may pass in your abort controller as nicely. No have to pass the abort signal - we'll create a signal from that controller for the abort technique. You can add question or queries as an possibility and zlFetch will create a question string for you robotically. Use this with GET requests. Fetch sets Content-Type appropriately depending on your physique information.