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

swagger-express-mock-not-found-conflict

v1.0.1

Published

Swagger mock util middleware

Downloads

8

Readme

Context

Mock middleware from swagger-express allows us to have a fully usable mocked API with zero logic code. It takes the swagger spec as a base and applies some intelligence, in order to automatically mock the implementation of controllers and datastore. The result is a cool express application responding to all HTTP requests as well as a decent demo data persistence store. The mock feature gets handy for prototyping, demo, and TDD implementation.

swagger-express-mock-not-found-conflict

This package provides the following two utils middlewares to work together with swagger-express Mock.

mockResourceNotFound

mockResourceNotFound: By default the Mock middleware consider POST and PATCH methods as the same operation. However by definition PATCH method can return a not found when a client attempted to apply a patch document to a non- existent resource but the patch document chosen cannot be applied to a non-existent resource. Basically mockResourceNotFound middleware will response with 404 if the resource to be updated or deleted does not exist.

mockPostConflict

If the API must return a 409 error for POST requests that lead to duplicated elements. The default behavior of the mock middleware considering PATCH and POST as the same operation and will not work. Using the mockPostConflict we may provide a property as a primary or unique key for the detection of duplicate items in one collection.

install

npm i swagger-express-mock-not-found-conflict

Basic Usage

...
const { mockResourceNotFound, mockPostConflict } = require('swagger-express-mock-not-found-conflict')
...
app.use(
  middleware.metadata(),
  middleware.CORS(),
  middleware.parseRequest(),
  middleware.validateRequest(),
  // notFound for PATCH and DELETE
  mockResourceNotFound(mockMemoryDB),
  // id is the primary/unique key that lead to conflict 409
  mockPostConflict(mockMemoryDB, 'id'),
  middleware.mock(mockMemoryDB)
)
...

Example

For a fully functional example please clone: the repo from here: https://github.com/osvaldo2627/swagger-express-mock-not-found-conflict

Running the example

After clone

cd swagger-express-mock-not-found-conflict
npm i
npm start

Note: The example launch a swagger-ui for testing: localhost:3000

Test

npm run test