Skip to content

Commit e593439

Browse files
authored
Remove the Fetch API article link (close #2954)
1 parent fd5e2fa commit e593439

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

src/v2/cookbook/using-axios-to-consume-apis.md

-2
Original file line numberDiff line numberDiff line change
@@ -172,8 +172,6 @@ This can be even further improved with the use of components for different secti
172172

173173
The [Fetch API](https://developers.google.com/web/updates/2015/03/introduction-to-fetch) is a powerful native API for these types of requests. You may have heard that one of the benefits of the Fetch API is that you don't need to load an external resource in order to use it, which is true! Except... that it's not fully supported yet, so you will still need to use a polyfill. There are also some gotchas when working with this API, which is why many prefer to use axios for now. This may very well change in the future though.
174174

175-
If you're interested in using the Fetch API, there are some [very good articles](https://scotch.io/@bedakb/lets-build-type-ahead-component-with-vuejs-2-and-fetch-api) explaining how to do so.
176-
177175
## Wrapping Up
178176

179177
There are many ways to work with Vue and axios beyond consuming and displaying an API. You can also communicate with Serverless Functions, post/edit/delete from an API where you have write access, and many other benefits. Due to the straightforward integration of these two libraries, it's become a very common choice for developers who need to integrate HTTP clients into their workflow.

0 commit comments

Comments
 (0)