Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

interfacer

Package Overview
Dependencies
Maintainers
1
Versions
14
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

interfacer

Module for working with REST API

  • 0.0.9
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
1
decreased by-66.67%
Maintainers
1
Weekly downloads
 
Created
Source

Interfacer.js

Interfacer.js is a convenient module for working with RESTful API from Client.

Key Features:

  • Unopinionated about frameworks you use
  • Highly customizable
  • Memoization by default
  • Simple error handling, that fits your system
  • Customizable query construction

How to install

yarn add interfacer

or

npm install interfacer --save

Configuration & Interface Creation

The most advanced feature, Interfacer.js provides, are 3 levels of configuration (Application level, Single Interface/Collection level, Request level). In every configuration level you can define things like defaultError, baseUrl, custom querybuilder and more. Each level of configuration overrides previous (more global ones), so you can change everything, mid-action, on the fly if you need to.

Don't panic as you'll see all them references to Redux like dispatch. Their's purpose is purely illustrative. you can provide any kind of function, that handles your data.

Application Level

import interfacer from 'interfacer';

const globalConfig = {
  baseUrl: 'http://localhost:8080/api',
  defaultError: new Error('Something broke'),
  errorHandler: ({error, message}) => dispatch({ type: 'API_ERROR', payload: message })
}

const createInterface = interfacer(globalConfig);

All of above settings will apply to every interface instance you create with this createInterface function, unless overwritten by later configurations in more "local" level.

Interface level

Also can be perceived as "collection level". In for example Redux I'd recommend to have one interface for each collection reducer. From server perspective, there is one interface per resource.

const localConfig = {
  defaultError: new Error('Articles API error'),
  querybuilder: myCustomQueryBuilder,
  headers: { 'Content-Type': 'text/html' }
  request: { mode: 'cors' },
  flatMethod: parseXMLFunction,
  errorHandler: err => dispatch({ type: 'API_ERROR', payload: err })
}

const articleInterface = createInterface('/articles', localConfig);

On Interface level you always specify resource. That is route that will be appended to baseUrl in all requests you do, with this interface. resource string is always passed to createInterface function as a first paramtere. Obviously you can (and will) have many different Interfaces.

Request level

This final and most local level references to a certain requests you make with your interface. Each call returns a promise with your flattened (see flatMethod) response.

const requestOptions = {
  query: { fields: ['title', 'author']},
  defaultError: new Error('Articles Collection failed to fetch')
};

articleInterface
	.getCollection(requestOptions)
  .then(data =>
  	dispatch({ type: 'RECIEVE_ARTICLES', payload: data })
  );

Overview

Once you've created your interface network and configured it, it's time for you to do some fetching. Every interface has following methods get, getCollection, update, create and remove. Once called, each function returns a Promise, that contains response of the fetch as a frist parameter. Here is their API annotation.

get

(id :string | number, requestConfig? :Object) => Promise<Response>

getCollection

(requestConfig? :Object) => Promise<Response>

create

(body :Object, requestConfig? :Object) => Promise<Response>

remove

(id :ID, requestConfig? :Object) => Promise<Response>

update

(id :string, body :Object, requestConfig? :Object) => Promise<Response>

API Reference

Config Properties

PropertyMeaningTypeDefault
errorError that gets sent to you via throwError fn once it occuresstring or object"unhandled"
defaultErrorIf no error is found, defaultError gets sent to youstring or object"unhandled"
errorHandlerFunction that gets called if error occurs. As first argument your error will be passedconsole.error
headersObject containting headers your request should haveobject"Content-Type": "application/json"
flatMethodFunction that will be used on raw response from the fetchfunction.json()
requestThis object will be added to request options. It's the same as pasting an object into second argument of fetch function{}
queryObject that gets passed to queryparser fnobject{}
baseUrlbaseUrl that your API runs onstring"/"
querybuilderFunction that transform query object into a query stringfunctionquerybuilder
makeBodyFunction that'll be run on body, right before request is made.functionbody => body

URL Queries

You can pass your own querybuilder into any config, but you can also use default one. Annotation of querybuilder looks like this

 querybuilder(query :Object) => string

Default querybuilder builds queries like this...

querybuilder({
  filters: 'over18',
  fields: ['title', 'years old']
});
// -> 'filters=over18&fields=title&fields=years%20old'

Keywords

FAQs

Package last updated on 26 Apr 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc