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

thingy-schema-validate

v0.0.5

Published

JSON schema validation for the thingy ecosystem - more primitive and simple than real JSON schemas.

Downloads

19

Readme

thingy-schema-validate

Background

In the regular communication between thingies, we call the routes similar as functions. There our arguments are all inside one JSON and our response is also one JSON.

However, because we have a gap of whild free network in between where anybody could create any mal-crafted request or response, we should validate these for being well-formed before further processing.

After some small research about JSON-schemas and JSON Type Definitions, once again the conclusion was drawn that directly building the validators we need seems to be far less of a headache.

Usage

Requirements

  • ESM importability

Installation

Current git version:

npm install -g git+https://github.com/JhonnyJason/thingy-schema-validate-output.git

Npm Registry

npm install -g thingy-schema-validate

Current Functionality

We have some "Enum" Types. We may import it into a validators-modulefile as:

import {
    NUMBER, STRING, STRINGHEX, STRINGHEX32, STRINGHEX64, STRINGHEX128, 
    BOOLEAN, ARRAY, OBJECT, NONNULLOBJECT, NUMBERORNULL, STRINGORNULL, 
    STRINGHEXORNULL, STRINGHEX32ORNULL, STRINGHEX64ORNULL, 
    STRINGHEX128ORNULL, BOOLEANORNULL, ARRAYORNULL
} from "thingy-schema-validate"

This way we may build schemas like this:

functionArgumentSchema = {
    argString: STRING
    argNumber: NUMBER
}

Then we may use the validate Function to validate any object for this schema

import { validate } from "thingy-schema-validate"

args = foundArgsFromAroundTheCorner()

try validate(args, functionArgumentSchema)
catch err then log "seems the args was invalid!"

Further steps

  • check if we need some more types
  • maybe improve performance? Fix bugs?

All sorts of inputs are welcome, thanks!


License

Unlicense JhonnyJason style