Currently the "currency" filter only accepts one argument: the currency
symbol. The number of decimal places is fixed as 2. This can cause
troubles with several currencies out there whose number of decimal places
can be 0 (e.g. Japanese Yen or Vietnamese Dong) or 3 (e.g. Jordanian
Dinar).
This commit modifies the filter to accept an extra optional argument:
decimal places, which defaults to 2. With this, one can write `{{ 1234 |
currency '¥' 0 }}` to properly display a Yen value. Backward
compatibility is maintained.
- Added test for checking prop to data clash
- Added test to ensure data function is only called once per strut
- Removed this._runtimeData uses 'data' for prop to data clash check
* fix 'Maximum call stack size exceeded' when recursively traverse an object
* remove semicolon
* simplify assignment expression
* add unit test for circular references detected in Watcher#traverse
- revert class update mechanism due to perf regression
- normalize array of (string|object) and objects into array of strings. this
simplifies the scenario for the rest of the code.
Since `text` is being used as the key in `cache.get(text)` and the
cache is checked *before* newlines were removed, the cache would always
miss if the input `text` had *any* newlines.
I updated `tagRe` to match tags which contain newlines, and added an
extra test case to ensure newlines outside of tags are preserved
This commit adds support for using multiple class names as key when
specifying a `:class` object, for example `<div :class="{ 'a b c': flag
}">`. Previously, doing so will trigger an uncaught
InvalidCharacterError, as spaces are not allowed in DOM tokens. Feature
request #2571 should also be satisfied by this commit.