Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

react-input-message

Package Overview
Dependencies
Maintainers
1
Versions
40
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-input-message

unopinionated form input annotation

  • 0.5.2
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
121
increased by10%
Maintainers
1
Weekly downloads
 
Created
Source

react-input-message

A small, completely unopinionated way, to display messages next to inputs based on events. Helpful for displaying input validation messages.

There is a frustrating trend in javascript form validation solutions that couple the view concerns of a form (hiding/showing of messages) with some specific data layer model, or abstraction. This often means that in order to use a form validator you also need to use a specifc js schema validator, or are tied into using a specifc validation library. react-input-message strives to provide just a solution to quickly and easily annotating form controls without requiring that you use a specific validation or data schema library.

Install

npm i -S jquense/react-input-message

Use

You render your inputs as you normally would, except that you wrap them inside a MessageTrigger component which will watch its child input for events.

render(){
  var messages = {
    name: ['name is required']
  }

  return (
    <MessageContainer 
      messages={messages}
      onValidationNeeded={handleValidationRequest}
    >
      <form>
        <div>
          <label>Name</label>
          {/* the `events` prop tells the MessageContainer what 
            * events to trigger a `onValidationNeeded` handler for */}
          <MessageSource for='name' events={[ 'onChange', 'onBlur']}>
            <input type='text' 
              value={this.state.name} 
              onChange={handleChange}
            />
          </MessageSource>

          {/* A `Message` Component will display field specific 
            * messages (as provided by the `messages` prop) */}
          <Message for='name'/>
        </div>

         {/* `MessageTrigger` will trigger a `onValidationNeeded` event for the entire
           * container, or just a specific group. */}
        <MessageTrigger type='submit'>
          Submit
        </MessageTrigger>
      </form>
    </MessageContainer>
  )

react-input-message exports four simple components:

MessageContainer

Props

  • onValidationNeeded: a handler that fires for each MessageSource component
  • messages: a hash of field names (for prop values) and either a string, or an array of strings
MessageSource

A MessageSource is a commponent that listens to its child for specific events. Generally this will be an input component

props

  • for: a field name or path
  • group: an arbitrary group name that allows inputs to be triggered together
  • activeClass: a class to be added to the input if its field is currently active
  • events: default(['onChange']) an array of prop handlers that the MessageSource will list on, and trigger a onValidationNeeded event in the Container
MessageTrigger

Simple component that will trigger onValidationNeeded for all or a group of inputs

  • component: The Component class that will render, the default is button
  • group: scopes the Trigger to a specific group, and will only trigger validation for inputs with the same group name
Message

Displays the actual messages for a field, the default implementation just concats the messages together with , but you can easily create custom Message components with the connectToMessageContainer() helper

connectToMessageContainer(componentClass)

in lieu of mixins you can use this helper function to wrap a component so that it passed the MessageContainer state as props. The following will be passed to your componentClass as props:

  • messages: will be for the specificed field (via the for prop)
  • active: if you provide a for prop this prop will be true or false based on whether there are any active messages
Validator(validationFn)

A very simple basic form validator class, to help manage input error state, use is completely optional. It is designed to nicely hook up to the MessageContainer component without being tightly coupled to it.

  • validate(field|fields, [ context ]) returns a promise that resolves with the valid state of the field. You can validate multiple fields by passing an array. You can also pass in a context object which will be passed to the validationFn
  • isValid: checks if a field is currently in an error state
  • errors([fields]): return a hash of errors, you can pass this object directly to a MessageContainer messages prop
let model = { name: '' }

// you instantiate the object with a function that determines if a field is valid or not
let validator = new Validator(function(fieldName, context){
  let isValid = !!context.model[fieldName]

  if ( isValid === false)
    return [ fieldName + ': is required!'] 
})

validator.validate('fieldName', { model: model })
  .then(function(isValid){
    //do something
  })

validator.isValid('fieldName')



FAQs

Package last updated on 16 Apr 2015

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc