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

@loopback/example-rest-crud

v6.0.1

Published

An example showing how to use @loopback/rest-crud to define default repository and controller classes

Downloads

121

Readme

@loopback/example-rest-crud

This is a basic example demonstrating how to use the default CRUD REST repository and controller with a single model class and datasource.

Overview

The Todo example can be simplified to use the default repository and controller classes provided by @loopback/rest-crud. With this package, there's no longer a need to define a repository or controller class for a model.

Given a Todo model and db datasource, create src/model-endpoints/todo.rest-config.ts and add the following configuration to it:

import {ModelCrudRestApiConfig} from '@loopback/rest-crud';
import {Todo} from '../models';

module.exports = <ModelCrudRestApiConfig>{
  model: Todo,
  pattern: 'CrudRest',
  dataSource: 'db',
  basePath: '/todos',
};

The pattern CrudRest means it will use the default CRUD REST repository and controller classes. The dataSource should correspond to the datasource you want to use with this model. Finally, the basePath should refer to the base path the controller will use.

Add the following import to src/application.ts:

import {CrudRestComponent} from '@loopback/rest-crud';

And the following component to the application constructor:

this.component(CrudRestComponent);

And there you go! Now the application should behave almost the same as the Todo example (with the exception of the geocoder service).

You can run the application by running the following from the root directory:

$ npm start

Server is running at http://127.0.0.1:3000

Contributions

Tests

Run npm test from the root folder.

Contributors

See all contributors.

License

MIT