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

roadhouse-mock

v1.1.0

Published

A set of factories to create simple mock handlers for CRUD data in Angular

Downloads

8

Readme

roadhouse-mock

A set of factories to create simple mock handlers for CRUD data in Angular.

Basic Example Setup

The most concise way to create mock handlers is like so

// A bunch of boilerplate up here so you are still in control
require( "angular-mocks" );
var rhMock = require( "roadhouse-mock" );
var data = {
    list: [ { key: "value 1" }, { key: "value2" } ],
    otherList: require( "./stuff" )
};

angular.module( "e2e-mocks", [ "ngMockE2E" ] )
.run( [ "$httpBackend", "APIRoot",
    function ( $httpBackend, APIRoot )
    {
        rhMock.setApiRoot( APIRoot );
        rhMock.$httpBackend = $httpBackend;

        // These are the lines where it gets good
        rhMock.create( "list", [ "GET", "POST" ], data.list );
        rhMock.create( "list/:itemId", [ "PUT", "DELETE" ], data.list );
        rhMock.create( "other-list", [ "GET" ], data.otherList );
    } ] );

angular.module( "App" ).requires.push( "e2e-mocks" );

Long-Form Example Setup

create( path, methods, list ) sets up handlers with the methods used below, which you can also use directly, if you like.

//... Just like before the `run` block above ...
.run( [ "$httpBackend", "APIRoot",
    function ( $httpBackend, APIRoot )
    {
        rhMock.setApiRoot( APIRoot );
        // rhMock doesn't need to know $httpBackend when used like this

        // GET a list
        $httpBackend.whenRoute( "GET", APIRoot + "list" )
            .respond( rhMock.createList( data.list ) );

        // POST to a list
        $httpBackend.whenRoute( "POST", APIRoot + "list" )
            .respond( rhMock.createPost( data.list ) );

        // PUT to a list
        $httpBackend.whenRoute( "PUT", APIRoot + "list" )
            .respond( rhMock.createPut( data.list ) );

        // DELETE from a list
        $httpBackend.whenRoute( "DELETE", APIRoot + "list" )
            .respond( rhMock.createDelete( data.list ) );

        // you can still use any typical handlers as well
        $httpBackend.whenRoute( "GET", APIRoot + "/other-list" )
            .respond( function ( method, url, data )
            {
                data = JSON.parse( data );
                if( data.email === userObj.email )
                {
                    return [ 200, data.otherList ];
                }
                return [ 401 ];
            } );
    }
] );
angular.module( "App" ).requires.push( "e2e-mocks" );

Additional Options

skipQueriesInList, default [ "skip", "take", "offset", "limit", "page", "rhcurrentpage", "search" ]

An array of params that will be ignored when filtering paged responses.

skipParamName, default "skip"

The parameter that the paged response will use to skip a number of items from the available list.

takeParamName, default "take"

The parameter that the paged response will use to take a number of items from the available list.