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

curio-binding-toolkit

v0.0.1

Published

A set of common React components used in binding project

Downloads

1

Readme

React Binding Toolkit

Description

A set of common React components used in binding project;

Usage

import {FormValidator, SMSButton} from "curio-binding-toolkit"

FormValidator

Example usage can be found in js/entries/test.tsx

Props

interface FormField {
    validators: InputValidator[]
    defaultValue: any
    errMsg: string
    inWhiteList?: boolean
}

interface InputValidator[] {
    (value: any) => boolean
}

interface Errors {
    [fieldName: string]: string | boolean
}

| Prop | Type | Note | | ---- | ---- | ---- | |fields|FormField[]|| |onError|(errors: Errors) => any||

Methods

| Method | Signature | Note | | --- | --- | --- | | set | (field: string, value: any) | Update field's value | | validate | (field?: string) | validate the value of field when field is provided, otherwise validate all fields |

  1. Parent component need to render input component by themself, and call FormValidator.set(f, v) in onChange() method;
  2. Parent component should call FormValidator.validate() before they submit the form;
  3. Parent compoennt should call FormValidator.validate(fieldName) after user complete the inputting of certain field; onBlur() handler is usually where FormValidator.validate(fieldName) should be called;
  4. Set a field's inWhiteList prop to true to skip this field when form is validating;

SMSButton

Props

| Prop | Type | DefaultValue | | ---- | ---- | ---- | |text |string| The default text displayed on the button| |disabledColor|string|The background color when button is disabled| "#fefefe" |countDownText|string|Text displayed on disabled button| "%s" |interval|number|The minimum interval between two sms send in second| 60 |handler|(success: any, fail: any) => any||

  1. countDownText is supposed to be a string that contains a %, where % will be replaced by the remaining time after which the user can send sms again;
  2. handler is the action when button is clicked. It receives two arguments: success and fail. Simply call them when sending sms success or fails; For example:
const handler = (success: any, fail: any) => {
    axios.post("/api/sms/send", {phone: "1234567"}).then(res => {
        if (res.data.code === 200) {
            success()
            alert("send sms successfully!")
        }
        else fail()
    }).catch(fail)
}

Calling success() will start the count down process, and call fail() will enable the button again, because we have already disabled it when the button is clicked;