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

generic-api-helper

v0.0.6

Published

Generic API helper to do HTTP request

Downloads

31

Readme

Generic API helper for Axios

En la mayoria de los casos usamos 4 endpoints y 4 HTTP Methods para todo, POST, GET, PUT, DELETE. Entonces ¿Por qué deberiamos tener una función para cada caso, si la gran mayoría de los funcionamientos son iguales? De tener putProductos, getCategorias, deletePedidos pasamos una función para cada HTTP method que utilizamos: httpCRUDEndpoint, simplemente con poner httpCRUDEndpoint('put', '/api/productos', {id: ObjectId}) hacemos lo mismo que crear una función especifica para cada endpoint.

Admite tres parametros, method, url, data.

/**
 * @description Esta función es utilizada para hacer queries de manera abstracta.
 * @async
 * @param {string} method - Metodo HTTP. Case insensitive, se transforma usando toLocaleLowerCase)
 * @param {string} url - Uniform Resource Locator (URL Del endpoint)
 * @param {Object} data - Objecto a utilizar como parametro en el req.body o req.query
 */

Cómo usar

Simplemente llamamos al endpoint con la URL y el método que necesitemos.Acá un ejemplo con getProductos.

Ejemplos 

const apiHelper = require("generic-api-helper"); //Importamos el apiHelper

export const getProductos = async (params) => {
  return await apiHelper.httpCRUDEndpoint("get", "/api/productos", params);
};

Como podemos ver, no es necesario ni siquiera envoler el helper en una función async. Simplemente podemos hacer en nuestro componente de React algo como: let data = await apiHelper.httpCRUDEndpoint("get", "/api/productos", params);

import httpCRUDEndpoint from "generic-api-helper"; //Importamos el apiHelper

export const getProductos = async (params) => {
  return await httpCRUDEndpoint("get", "/api/productos", params);
};

// httpCRUDEndpoint(method, url, params);

Funcionamiento

TL;DR httpCRUDEndpoint es una funcion async que nos permite elaborar peticiónes usando una AxiosInstance mapeando el string pasado en method a unas funciones cuyo key value son del tipo "delete": async (url, data) => {AxiosInstance.delete(...)} en un JSON.

Primero armamos un mapeo de las llamadas con cada HTTP Method y lo llamamos method callers.

const methodCallers = {
  post: async (url, data) => {
    if (data) {
      return await ajax.post(url, data);
    } else {
      return await ajax.post(url);
    }
  },
  get: async (url, data) => {...},
  put:  async (url, data) => {...},
  delete:  async (url, data) => {...},
};

Luego preparamos dos mockup answers, una para cuando tenemos un error de JavaScript y otra para cuando tenemos un error de axios o una AxiosInstance error (Esta parte necesita refactorizarse un poco, ver Handling errors| Axios).

let mockupResponse = {
    serviceUnavailable: {
      data: {
        error: {
          message: "Servidor inalcanzable",
        },
      },
    },
    error: (msg) => {
      return {
        data: {
          error: {
            message: msg,
          },
        },
      };
    },
  };

y adicionalmente, una variable que actuará de flag por si no pasamos un método HTTP válido

let notACRUDMethod = false; //Se pondrá en true si method no es "post, get, put, delete"