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

@netsells/laravel-api-parser

v2.0.0

Published

Parse Laravel API responses

Downloads

107

Readme

npm version Build Status codecov Mutation testing badge

Laravel API Parser

Parse responses from Laravel API REST endpoints and extract meaningful errors related to your form fields

Installation

yarn add @netsells/laravel-api-parser

Usage

Note: it currently only works with axios response objects or any object with the same duck type.

Import the ResponseParser class and instantiate it, passing in any custom options you would like to use

import ResponseParser from '@netsells/laravel-api-parser';

const responseParser = new ResponseParser();

const response = await axios.post('/foo/bar', data);

const errors = responseParser.getErrors(response);

The getErrors returns an object containing the errors for the fields passed in. It may also return an object with a key of null representing a generic error for the entire response, rather than a single field.

For a 422 error it may return:

{
    email: 'You must enter a valid email'
}

For a 500 error it will return:

{
    [null]: 'Something went wrong, sorry about that'
}

Customisation

Config

When instantiating the class, you can pass in an object with the following keys to override certain behaviour

fallbackErrorMessage

The error message used as the last resort, when no other errors could be parsed.

new ResponseParser({
    fallbackErrorMessage: 'Woops, something went wrong! Please try again later',
});

Overrides

You can override the ResponseParser class to change the functionality of it.

When parsing errors, getErrors will look for a function based on the status of the response, e.g. getErrorsFor404 for a 404 status. If this doesn't exist, it will fallback to a function for the range of the status, in this case getErrorsFor4XX. Finally if that doesn't exist, it will return the fallback error message.

So if you wanted to added custom errors for 404 responses, you could do this:

import ResponseParser from '@netsells/laravel-api-parser';

class MyResponseParser extends ResponseParser {
    getErrorsFor404() {
        return {
            [null]: 'Not found!',
        };
    }
}

const responseParser = new MyResponseParser();

const response = await axios.get('/my-model/12'); // doesn't exist

const errors = responseParser.getErrors(response); // { [null]: 'Not found!' }

Contributing

Pull requests are welcome! Ensure each PR includes a test case (which would fail without your changes) and that your build passes.