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

oe-input

v2.3.0

Published

oeCloud implemenetation of paper-input with additional behaviors

Downloads

9

Readme

<oe-input>

<oe-input> is a control for text input based on Polymer's paper-input control with following additional features.

  1. control level validations
  2. model-level/cross-field validations. When any UI control is placed on the form, the control needs to be 'aware' of 'which property' on the model it is bound to. This is required specially since, many times two or more controls take part in deciding the model validity. (cross-field-validations)
  3. support internationalization of labels and error-messages out of box.
  4. oe-input adds a little red-asterisk if the field is 'required'.
    <oe-input required field-id="accountName" label="Account Name"></oe-input>

This repo also consists of the following components

  • oe-input
  • oe-decimal
  • oe-input-masked
  • oe-json-input
  • oe-textarea

oe-decimal

<oe-decimal> is a control for capturing number inputs. In addition to <oe-input>, it supports handling of decimal display, parsing and formatting.

oe-input-masked

<oe-input-masked> is a control for capturing text input based on oe-inputcontrol with following additional features.

  1. mask the each char with a specified char, based on a RegExp pattern
  2. mask the each matched pattern with a specified string, based on a RegExp pattern
  3. add specified number of mask char(s) at the end of the specified input.

oe-json-input

<oe-json-input> is a control for multiline text input based on Polymer's paper-textarea control with following additional features.

  1. control level validations
  2. model-level/cross-field validations. When any UI control is placed on the form, the control needs to be 'aware' of 'which property' on the model it is bound to. This is required specially since, many times two or more controls take part in deciding the model validity. (cross-field-validations)
  3. support internationalization of labels and error-messages out of box.
  4. oe-json-input adds a little red-asterisk if the field is 'required'.

oe-textarea

<oe-textarea> is a control for multiline text input based on Polymer's paper-textarea control with following additional features.

  1. control level validations
  2. model-level/cross-field validations. When any UI control is placed on the form, the control needs to be 'aware' of 'which property' on the model it is bound to. This is required specially since, many times two or more controls take part in deciding the model validity. (cross-field-validations)
  3. support internationalization of labels and error-messages out of box.
  4. oe-textarea adds a little red-asterisk if the field is 'required'.
    <oe-textarea required field-id="accountName" label="Account Name"></oe-textarea>