Node.js module that abstracts the process of consuming a REST endpoint.
npm install rest-facade
When creating a new client, a URL must be given as first arguments. If the URL have dynamic params, those variable params must be marked with the colon notation, as shown below.
var rest = require('rest-facade');
var options = {
headers: {
Authorization: 'Bearer token'
}
};
var Users = new rest.Client('http://domain.com/users/:id', options);
// The URL can have several dynamic params.
var UserVideos = new rest.Client('http://domain.com/users/:userId/videos/:slug');
The getAll()
method can take an optional object as first parameters specifying the URL params. Considering the UserVideos model from last example:
// Retrieve all videos from the user with ID 4.
// This will resolve to a "GET http://domain.com/users/4/videos" request.
UserVideos
.getAll({ userId: 4 })
.then(function (users) {
console.log(users.length, 'users retrieved');
});
// Retrieve the user with ID 4.
Users
.get({ id: 4 })
.then(function (user) {
console.log(user);
});
The create method can be called using several signatures.
create(data)
returns a Promise.create(urlParams, data)
returns a Promise.create(data, callback)
doesn't return a promise.create(urlParams, data, callback)
doesn't return a promise.
Users
.create({ firstName: 'John', lastName: 'Doe' });
.then(function (user) {
console.log('User created');
});
UserVideos
.create({ userId: 4 }, { title: 'Learning Javascript', slug: 'learn-javascript' })
.then(function (video) {
console.log('User video created');
}):
As it was the case with the create()
method, delete()
can also be called with different signatures.
delete(urlParams)
returns a Promise.delete(callback)
returns a Promise.delete(urlParams, callback)
doesn't return a Promise.
Users
.delete({ id: userId })
.then(function () {
console.log('User deleted');
});
// This will resolve to: DELETE http://domain.com/users/videos/learn-javascript
UserVideos
.delete({ slug: 'learn-javascript' })
.then(function () {
// ...
});
As with the previous methods, an object with the URL parameters must be provided as first argument. The second argument must be an object with the new data.
Users
.update({ id: userId }, data)
.then(function () {
console.log('User updated');
});
All methods support callbacks. However, if a callback function is given no promise will be returned. Callbacks must always be provided after all other function arguments. E.g.:
Users.getAll(function (err, users) {
console.log(users.length, 'users found');
});
All methods accept an object with URL params as first argument. The properties in this object will be used to format the URL as shown above. However, the properties defined in this object, but not in the endpoint URL, will be added as query string params.
var Users = new rest.Client('http://domain.com/users/:id');
Users.get({ id: 1 }); // Resolves to http://domain.com/users/1
Users.getAll({ page: 1, pageSize: 10 }); // Resolves to http://domain.com/users?page=1&pageSize=10
There may be some cases when you are working with an API that follows a different naming convention, and it is not really clean to have mixed naming conventions in our code.
// Not good.
Users.getAll({ page: 1, 'page_size': 10 });
You can solve this problem by specifing a naming convention when creating the Rest Client. The naming convention can be any of snakeCase
, camelCase
, pascalCase
, paramCase
, or any other implemented by the change-case library.
var Users = rest.Client('http://domain.com/users/:id', { query: { convertCase: 'snakeCase' }});
Users.getAll({ page: 1, pageSize: 10 }); // Will resolve to http://domain.com/users?page=1&page_size=10