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

@prisma-utils/nestjs-request-parser

v1.2.0

Published

This package allows for automatically parsing query parameters and map them to a `prisma` compatible format to be automatically appended to `FindMany` calls.

Downloads

6

Readme

Request-Parser

This package allows for automatically parsing query parameters and map them to a prisma compatible format to be automatically appended to FindMany calls.

Usage

First, you need to add the decorator to a method in your controller.

@Controller()
export class UserController {
  constructor(private readonly userService: UserService) {}

  @Get()
  getAll(@RequestParser() requestParams: ParsedQueryModel) {
    console.log(requestParams);
    return this.userService.getAll(requestParams);
  }
}

Then call the route as follows:

example.com/api/users?sort=-id,name&limit=20&page=5&filter={"email": {"endsWith": "googlemail.com"}}

will return users with an email address that ends with googlemail.com. The route will return 20 entries from the 5th page (i.e., entry 81 - 100). Entries are ordered by id (descending) and name (ascending).

Query Parameter Schema

| name | description | default | | -------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------- | | sort | order by attribute. Comma separated list of attributes. - in front of a attribute (i.e., -id) means order by attribute descending. | id | | limit | limit the result to a specific number of entries. Provides the possibility to set a maximum value as well | 20 | | page | describe the page that should be retrieved (use in combination with limit) | 1 | | filter | describe an additional filter/where clause that may be appended to the findX call. | {} |

Filter

The filter parameter should be passed as an object. Please note that this library does not validate / properly parse the passed object. Basically, you are free to use whatever style / format you would like. It would, however, be a good idea to use a similar idea as Prisma does (see the official documentation).

The filter parameter value must be JSON.parseable, otherwise the default value ({}) is used.

Default Configuration

{
  "limitParamName": "limit",
  "limitDefaultValue": 20,
  "maxLimit": 100,

  "pageParamName": "page",
  "pageDefaultValue": 1,

  "orderParamName": "sort",
  "orderDefaultValue": "id",

  "filterParamName": "filter",
  "filterDefaultValue": {}
}

The default configuration can be overwritten when using the Decorator. For example, a custom sort order can be defined via

@Controller()
export class UserController {
  constructor(private readonly userService: UserService) {}

  @Get()
  getAll(
    @RequestParser({ orderDefaultValue: '-createdAt,name' })
    requestParams: ParsedQueryModel,
  ) {
    return this.userService.getAll(requestParams);
  }
}

This library was generated with Nx.

Building

Run nx build request-parser to build the library.

Running unit tests

Run nx test request-parser to execute the unit tests via Jest.