How Mini Program simply encapsulates http to access the network library
This article mainly explains "how Mini Program simply encapsulates http to access the network library". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "Mini Program how to simply encapsulate http to access the network library".
The code is as follows:
Var HOST = 'https://localhost/lendoo/public/index.php/';
/ / website request API, unified as post
Function post (req) {
/ / initiate a network request
Wx.request ({
Url: HOST + req.uri
Data: req.param
Header: {
"content-type": "application/x-www-form-urlencoded"
}
Method: 'POST'
Success: function (res) {
Req.success (res.data)
}
Fail: function (res) {
Console.log (res)
}
})
}
/ / Export module
Module.exports = {post: post
}
The front-end call can then do this:
Var http = require ('.. /.. / utils/http.js')
...
Http.post ({
Uri: http.orderListUri
Param: {
Third_session: wx.getStorageSync ('third_session')
}
Success: function (data) {
That.setData ({
OrderList: data
});
}
});
Generally speaking, when you write your own interface for your own use, the method method or header is agreed upon, so you don't have to repeat it.
Header: {
"content-type": "application/x-www-form-urlencoded"
}
Method: 'POST'
The fail callback method can also be handled uniformly; furthermore, the code value in the success callback can be further judged and the specific error codes can be handled uniformly, such as jumping to the login page.
Thank you for your reading, the above is the content of "how Mini Program simply encapsulates http to access the network library". After the study of this article, I believe you have a deeper understanding of the problem of how Mini Program simply encapsulates http to access the network library, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
