npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

hiep294-apiconnection

v1.0.2

Published

initial

Downloads

2

Readme

Basic API Connection

This module and module 'hiep294-route' are a couple. This module is to use for client side.

Example

Suppose that in app my todo list, a todo has the following fields: _id(created automactically by mongodb), title, isCompleted

Create this todoAPIConnection.js in the app

import ApiConnection from 'hiep294-apiconnection'

const todoAPIConnection = ApiConnection({
  url: '/api/todos',
  actions: ['index', 'create', 'update', 'delete']
})

export default todoAPIConnection

Above file will exports to an object todoAPIConnection may include the following format in overview:

{
  index: () => {}, /* if actions include 'index' */
  create: () => {}, /* if actions include 'create' */
  update: () => {}, /* if actions include 'update' */
  delete: () => {}, /* if actions include 'delete' */
}

In detail of todoAPIConnection

  • Note: handleSuccess, handleInvalid, handleFailedConnection which are below are callbacks which are defined by own developer while developing front-end service, and not be defined by this module.

1. todoAPIConnection.index = (handleSuccess, handleFailedConnection) => {/* content code defined in 'hiep294-apiconnection' module */}

Next common process: handleSuccess(responseItems)

  • when this method is called, if success, it will run handleSuccess(responseTodos), with responseTodos array is filtered from API response. The client side can use them to print out in the screen

2. todoAPIConnection.create: (todoItem, handleSuccess, handleInvalid, handleFailedConnection) => {/* content code defined in 'hiep294-apiconnection' module */},

Input: todoItem is passed from client side

Next common processes: handleSuccess(responseItem) or handleInvalid(responseErrors)

  • if creating todoItem successfully, it will run the method handleSuccess(responseItem), with responseItem is filtered from API response, so the developer can use it to add in client.
  • if creating todoItem un-successfully and because of invalid input, it will run the method handleInvalid(responseErrors), with responseErrors array is filter from API response

3. todoAPIConnection.update = (todoItem, handleSuccess, handleInvalid, handleFailedConnection) => {/* content code defined in 'hiep294-apiconnection' module */},

Input: todoItem is passed from client side, and should include key _id

=> Next common processes: handleSuccess() or handleInvalid(responseErrors)

  • if updating todoItem successfully, it will run the method handleSuccess().
  • if updating todoItem un-successfully and because of invalid input, it will run the moethod handleInvalid(responseErrors), with responseErrors array is filter from API response

4. todoAPIConnection.delete = (_id, handleSuccess, handleInvalid, handleFailedConnection) => {/* content code defined in 'hiep294-apiconnection' module */}

Input: _id of item in need of deleting

Next common processes: handleSuccess() or handleInvalid(responseErrors)

Change log

  • 1.0.2: more info about example