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

irrelon-schema-model

v0.0.6

Published

A library that extends the functionality of Irrelon Schema (npm i irrelon-schema) and adds the ability to instantiate, return and update models based on existing schemas.

Downloads

7

Readme

Irrelon Schema Model

A library that extends the functionality of Irrelon Schema (npm i irrelon-schema) and adds the ability to instantiate, return and update models based on existing schemas.

If you use "Schema" from this library it also extends the Schema class from irrelon-schema and adds the ability to create a new model constructor based on a schema e.g.

const {Schema} = require("irrelon-model-schema");
const UserSchema = new Schema({
	"name": {
		"type": String,
		"required": true
	},
	"age": {
		"type": Number,
		"required": false
	}
});

// The extended schema class from irrelon-model-schema supports
// setting a REST endpoint that should be used for CRUD manipulation
// of models
UserSchema.endPoint("/api/v1/user");

// The extended schema class also supports specifying an API object
// that exposes CRUD methods that implement the API interface described
// below in this document. The schema can use the API interface to call
// the REST endpoint via HTTP/s in order to apply CRUD operations.
UserSchema.api({
	// C(RUD)
	post: (url, data, options) => {
		Promise.resolve({
			err: {
				msg: "",
				token: "",
				details: {}
			},
			data: {},
			status: 200
		});
	},
	
	// (C)R(UD)
	get: () => {},
	
	// (CR)U(D)
	put: () => {},
	patch: () => {},
	
	// (CRU)D
	delete: () => {}
});

// Create a model constructor
const UserModel = UserSchema.model();

// Now we can get a user by id through the model
const myUser = await UserModel.findById(1);

// myUser is now an instance of UserModel with the data from
// the API endpoint matching the ID: 1 - if there was an error
// then the myUser instance will not be populated and will
// be in an error state. You can check this by calling
// UserModel.error(myUser)
myUser.name = "My New Name";

// Now we've modified the name, let's save it back to the API
// internally this will call the API patch method
myUser.save().then((response) => {
	// Check response and do whatever application logic you like
	// response conforms to the successResponse or failureResponse
	// schemas.
});

// If we want to overwrite (PUT) the model instead of partial
// updating (PATCH) we use the model method "overwrite()" instead:
myUser.overwrite().then((response) => {
	// Check response and do whatever application logic you like
	// response conforms to the successResponse or failureResponse
    // schemas.
});