Axios vs. Fetch API: Selecting the Right Tool for HTTP Requests #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
llqqssttyy
requested changes
Aug 10, 2024
Comment on lines
314
to
338
| const axios = require('axios'); | ||
|
|
||
| // 요청의 기본 URL 정의 | ||
| const baseURL = 'https://jsonplaceholder.typicode.com/todos'; | ||
|
|
||
| // 요청을 위한 URL 정의 | ||
| const urls = [`${baseURL}/1`, `${baseURL}/2`, `${baseURL}/3`]; | ||
|
|
||
| // Axios 요청 프라미스 배열 생성 | ||
| const axiosRequests = urls.map((url) => axios.get(url)); | ||
|
|
||
| // `axios.all()`을 사용하여 여러 요청을 동시에 전송 | ||
| axios | ||
| .all(axiosRequests) | ||
| .then( | ||
| axios.spread((...responses) => { | ||
| // 모든 요청의 응답 처리 | ||
| responses.forEach((response, index) => { | ||
| console.log(`Response from ${urls[index]}:`, response.data); | ||
| }); | ||
| }) | ||
| ) | ||
| .catch((error) => { | ||
| console.error('Error fetching data:', error.message); | ||
| }); |
There was a problem hiding this comment.
오 여기 fetch로 만드는 예시가 아니라 axios 예시예용!
Comment on lines
+97
to
+110
| fetch('https://jsonplaceholder.typicode.com/todos') | ||
| .then((response) => { | ||
| if (!response.ok) { | ||
| throw Error(`HTTP error: ${response.status}`); | ||
| } | ||
| return response.json(); | ||
| }) | ||
| .then((data) => { | ||
| console.log('Data received:', data); | ||
| }) | ||
| .catch((error) => { | ||
| console.error('Error message:', error.message); | ||
| }); | ||
| ``` |
There was a problem hiding this comment.
이건 그냥 제안인데, 들여쓰기가 tab이 아니라 띄어쓰기 2번이면 코드 가독성이 더 좋을 것 같아요!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
현재 저희 팀은 fetch를 사용하고 있는데요.
프로젝트를 시작하기 전에 무작성 axios를 사용하려고 했던 점이 떠올랐습니다.
그냥 다들 프로젝트에서 axios를 사용한다는 이유만으로요.
글을 선정할 때, 기술검토에 지니가 올린 axios가 필요한 이유가 떠올라서 그렇다면 axios와 fetch의 차이는 뭘까? 이것도 모르고 axios를 사용하려고 했다! 는게 떠올라서 한번 찾아봤습니당
한눈에 읽기!