Tags from vue-autoNumeric

v1.2.6: Fixes #24 VueAutonumeric value prop validator should accept strings

2018-09-14T19:07:47Z

Fixes #24 VueAutonumeric value prop validator should accept strings

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.2.5

2018-05-25T19:54:10Z

Fixes #14 The `readOnly` option is not respected for non-input tags (…

…`contenteditable` is always set to `true`)

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.2.4

2018-05-25T19:28:02Z

Fixes #18 Require of AutoNumeric is ES6 module and not the distributi…

…on version

Fix how using vue-autonumeric with a CDN did not work since the external library it searched was in lowercase.
Update the documentation about using `vue-autonumeric` in an ES6 module setup with Webpack

Important note:
- We need to use `<npmPath>: 'AutoNumeric'` in the `vue-autonumeric`'s webpack configuration since we want the user to be able to just use a CDN link to the AutoNumeric library and make sure `vue-autonumeric` will correctly use this name (since it's exported as `AutoNumeric`, with this case).
- However if you are using `vue-autonumeric` in an ES6 module setup with a bundling tool (ie. Webpack), then you'll need to declare in your project an alias so that Webpack will know how to recognize the correct library name case.
- The alias configuration example for Webpack:
```js
resolve: {
extensions: ['.js', '.vue', '.json'],
alias : {
'~' : resolve('node_modules'),
'@' : resolve('src'),
'AutoNumeric': resolve('node_modules/autonumeric/dist/autoNumeric.min'),
},
},
```

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.2.3: Fixes #15 Prop Validation Returns Error if Empty String

2018-05-09T21:34:33Z

Fixes #15 Prop Validation Returns Error if Empty String

Fixes #16 build fails on linux

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.2.1

2018-05-08T02:00:53Z

Update the examples with another way to set the empty value, via the …

…v-model

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.2.0: Simplify how the decimal places are set

2018-03-27T21:21:50Z

Simplify how the decimal places are set

In `v1.1.*`, whenever the options were changed, the number of decimal places for the `rawValue` was calculated based of the previous options, and not only the new given options.
This was useful when two vue-autonumeric components shared the same v-model, but different options that have different values for the `rawValue` decimal places count.

For instance if one of the `vue-autonumeric` component had a `decimalPlaces` option set to `2`, and another set to `5`, then when the user modified the value of one of those components, vue-autonumeric would detect a programmatic value change in the other component (since it did not come from a user interaction), and it would then use `set()` to set the new value.
The first component would drop the additional decimal places when using `set()`...which in turn would make the other components aware of that new value change, and the second component would then use that new cropped value as well.

However, this special decimal places management is complexifying the code quite a bit, and is not 100% effective since some use cases were difficult, if even possible, to manage.
This `rawValueDecimalPlaces` *hack* is now reverted to a more sane and legible code.

From now on, the user will have to explicitly declare the `rawValueDecimalPlaces` value when updating the options, if he does not want to lose the precision when switching options.

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.1.0

2018-03-01T02:55:41Z

Fix issue #10 When using an object to modify both the `:value` and `:…

…options` props, the options is not always modified before the value

Fix the issue where updating the `options` to new ones with a higher `decimalPlacesRawValue` loses the additional decimal places
Now allows to update the `options` by passing an array of options (with objects and predefined option names)

When the `options` and `value` are both set at the same time, `vue-autonumeric` now always update the `options` first, before setting the `value`.
- This allows to use objects with the value and a predefined option name to modify the vue-autonumeric component.
- Note: There is a know bug yet; if you use multiple `vue-autonumeric` component sharing the same `v-model` but *different* options, changing the value/option *may* not work correctly.
- This is due to the fact that when vue-autonumeric detects a value change, it `set()` it since it does not come from a user interaction.
- However if one of the `vue-autonumeric` component has a `decimalPlaces` option set to `2`, and another set to `5`, then the first component will drop the additional decimal places when using `set()`...which in turn will make the other component aware of that new value change, and the second component will then use that new cropped value as well.

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.0.7

2018-02-27T02:23:00Z

Fix issue #9 Modifying the `options` will always lose the decimal pla…

…ces precision after `2` places

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.0.6

2018-02-27T00:55:13Z

Fix issue #8 Add a new `resetOnOptions` props so that updating the `o…

…ptions` one first reset to the default options

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>

v1.0.5

2018-02-01T22:43:21Z

Fix issue #2 Allow the component to generate any supported Html eleme…

…nt instead of only `<input>`

Signed-off-by: Alexandre Bonneau <alexandre.bonneau@linuxfr.eu>