I suggest to include suffix it would be useful for the unit

example:

150 sqm, 6 ft and 5 km

To reproduce the error or describe your requirement with a jsfiddle url would be appreciated:

• Fork this with vanilla JS component: https://jsfiddle.net/nosir/kbaxx64s/
• Fork this with React JS component: https://jsfiddle.net/nosir/gLLsrxxf/

If it's mobile related, please specify your devi

e.g. isPassportNumber, etc.

In the current API documentation https://github.com/selectize/selectize.js/blob/master/docs/api.md, under the "items" section, the addItem function does not describe what type or format should the value argument be. It was only after a dug in that I realized it takes a single argument which should be equal to the value attribute of the option tag. I assumed, the type of value argument would

（必填）这个需求解决了什么问题 What problem does this feature solve

?表格内有一个或多个操作按钮，我希望在点击这些按钮后显示loading，并在稍后处理完毕后恢复。

（必填）请填写问题链接来描述为什么无法实现该功能，例如（jsfiddle、codesandbox、jsrun） Reproduction link

?如果要实现这样的功能，就需要使用 $event 把原生DOM 事件传入处理方法，但目前vxe-button好像无法这样传入（表格内用原生非vxe-按钮要单独调样式）。

The README and provided example has:

let suggestions = states().filter((state) => {
    return state.name.toLowerCase().slice(0, inputLength) === inputValue
  })

I think it should be something equivalent to:

const suggestions = states().filter(
  state =>
    inputLength > 0 &&
    state.name.toLowerCase().slice(0, inputLength) === inputValue
)

Otherwise the sug

It would be nice to remove some useless backets on documentation code.

Example:

<TextInputMask
  type={'cpf'}
  value={this.state.cpf}
  onChangeText={text => {
    this.setState({
      cpf: text
    })
  }}
/>

It would be better a example like this

<TextInputMask
  type='cpf'
  value={this.state.cpf}
  onChangeText={text => {
    this.setState({
      

In the documentation you say to call InputSystem.RegisterTemplate to register a custom device. But this does not seem to exist.

I'm trying to use Hyperform to detect when the form switches between an invalid and valid state so I can switch disabling of the submit button.

If I monitor the "valid" event on the form it keeps getting triggered even though elements within the form are still invalid.

If I run form.checkValidity() on startup each field will indicate an "invalid" event and checkValidity returns false. It see

There's this Tested Terminals section in most of the READMEs. What does this exactly mean? Let's say I'd like to add Terminal.app, iTerm2.app, etc. on macOS. I do not expect any issues, but you never know.

What's the procedure here? Was trying to find a test tool, list of manual steps, etc. but can't find anything.

Unless I've misunderstood the documentation, it doesn't seem like it's possible to have an arbitrary number of trailing arguments.

Let's say you want to write your own version of cat(1).

Based on the documentation, it seems like I should be able to use flaggy.TrailingArguments to get at the list of zero or more input files.

Unfortunately, if you actually try to use trailing arguments

I think it'll be useful if we can an option to display the chips under the input box instead of at the top as in cases when there are a lot of chips, the input keeps shifting down. it'll be nice to have the input stay at the top and the chips displayed under it. Take a look at the following pic.
![long list](https://cloud.githubusercontent.com/assets/3509404/21218405/714d870a-c2eb-11e6-9be2-c8f61

Hello,

It may seem not important but it speeds up a lot searching. Otherwise the only way is to make text search ...

Thanks

Hi, in the examples you have a findFilm method that has this line of code:

const regex = new RegExp(${query.trim()}, 'i');

But if you type special characters in the autocomplete textinput (like + and others) it will crash the app. Special characters must be escaped.

An example fix:
const regex = new RegExp(${query.trim().replace(/[-[]/{}()*+?.\^$|]/g, "\$&")}}`, 'i