Releases: vuejs/vue
Releases · vuejs/vue
v0.10.6
- fix
v-styleerror when value is falsy or a number. ( thanks to @dmfilipenko ) - fix the built-in
currencyfilter error when value is a string ( thanks to @dmfilipenko ) - fix
Vue.requirefor building with Component v1.0+ ( thanks to @kewah ) - Allow template nodes to be passed as a template option ( thanks to @jordangarcia )
vm.$destroy()now accepts an optional argumentnoRemove. When passed in astrueit will leave the vm's DOM node intact after the vm is destroyed.
v0.10.5
This is a bug fix release.
Improvements
- mixin methods are now properly tracked in computed properties.
v-stylenow respects the!importantsuffix. (#278)lazyoption is now automatically inherited if child VM doesn't have this option explicitly set. (#284)v-onnow works properly on iframes from the same origin. (#290)
Fixed
- #249 Fixed transitions on some Android 4.1 devices (thanks to @bpierre)
- #253 Fixed parsing error on attribute names containing colons
- #267 Removed extra
cloneNodeinv-partial(thanks to @dyu) - #276 & #281 Fixed child vms removed before parent's transition finishes
- #282 Fixed
v-withnot processed before other directives - #288 Fixed
v-withcircular updates
v0.10.4
New
- Uses more robust template to DocumentFragment conversion so that table/option elements are properly handled, and SVG tags are created with proper namespace.
Changed
- When using
v-repeaton an Array of primitive values, changing$valuefrom the repeated instance will no longer sync the change back to the original Array. See explanation in b50e5a5
Fixed
v0.10.3
v0.10.2
v0.10.1
v0.10.0: Blade Runner
"A coding sequence cannot be revised once it's been established." -Tyrell
New
- Literal directives can now contain interpolation tags. These tags will be evaluated only once at compile time. An example usage is conditionally decide which component to instantiate with
v-component="{{type}}". Doc. - Attributes listed in the
paramAttributesoption now accept mustache interpolations too. They will also only be evaluated once. v-repeatnow accepts an argument which will be used as the identifier for the wrapped object. This allows more explicit property access in repeaters. Doc.- Added
v-viewdirective which binds to a string value and dynamically instantiate different components using that string as the component ID. Doc. - Added
filterByandorderByfilters forv-repeat. Doc. - Custom filters that access properties on its
thiscontext will be considered computed filters. Doc. - You can now access the event in
v-onhandler expressions as$event. Example:<a v-on="click:handle('hello', $event)">Hello</a> - Interpolation delimiters can now be customized via the
delimitersglobal config option. Example:Vue.config({ delimiters: ["[", "]"] })will change the matched interpolation tags to[[ ]]for text bindings and[[[ ]]]for html bindings.
Changed
{{>yield}}syntax has been deprecated. A Web Components spec compatible content insertion mechanism using<content>elements has been introduced. Doc.- To use a component as a custom element, the component ID must now contain a hyphen (
-). This is consistent with the current custom element spec draft. v-repeatArrays' augmented methods have been renamed fromsetto$set(index, value)andremoveto$remove(index | value). The prefix better differentiates them from native methods. Thereplacemethod has been removed.- When iterating over an Object with
v-repeat, the object no longer gets a$repeaterarray. Instead, the object is now augmented with two methods:$add(key, value)and$delete(key), which will trigger corresponding view updates. v-ifnow creates and destroys a child ViewModel instance when the binding value changes, instead of simply removing/inserting the DOM node. In addition, it can no longer be used withv-repeat. Usev-showor the new built-in array filters instead.v-withcan no longer be used alone. It now must be used with eitherv-componentorv-view.v-componentcan also be used as an empty directive just to create a child VM using the defaultVueconstructor.- Production build now strips all warnings and debug logs. To leverage
debug: true, use the development version. The development version now has more detailed warning messages.
Fixed
event.stopPropagation()andevent.preventDefault()insidev-onhandlers now work as expected.parentoption now works properly when used inVue.extend- Mustache bindings inside
<textarea>are now properly interpolated before being set as value.
Internal
v-component,v-withandv-ifhave been re-written for a cleaner compile flow.v-repeathas been re-written to use refined diff algorithm which triggers minimum DOM manipulations when the array is set to a different instance containing overlapping elements. This makes it efficient to pipe an Array through filters.templateoption now directly clones native<template>'s content when available.- Overall performance improvements for both initialization and rendering.
0.10.0 Release Candidate
- Build: https://raw.github.com/yyx990803/vue/0.10-rc/dist/vue.js
- Install via Component:
component install yyx990803/[email protected] - Install via NPM:
npm install yyx990803/vue#0.10.0-rc
New
- Literal directives can now contain mustache interpolation tags. These tags will be evaluated once at compile time. An example would be conditionally choose which component to create with
v-component="{{type}}". - Attributes listed in the
paramAttributesoption now accept mustache interpolations too. They will also only be evaluated once. v-repeatnow accepts an argument which will be used as the identifier for the wrapped object. This allows more explicit property access in repeaters.- Added
v-viewdirective which binds to a string value and dynamically instantiate different components using that string as the component ID. See the updated routing example. - Added
filterByandorderByfilters forv-repeat. example - Custom filters that access properties on its
thiscontext will be considered computed filters. Any directive that uses a computed filter will be forced into a computed directive even when the binding is a simple keypath. - You can now access the event in
v-onhandler expressions as$event. Example:<a v-on="click:handle('hello', $event)">Hello</a> - Interpolation delimiters can now be customized via the
delimitersglobal config option. Example:Vue.config({ delimiters: ["[", "]"] })will change the matched interpolation tags to[[ ]]for text bindings and[[[ ]]]for html bindings.
Changed
- To use a component as a custom element, the component ID must now contain a hyphen (
-). This is consistent with the current custom element spec draft. v-repeatArrays' augmented methods have been renamed to$set(index, value)and$remove(index | value)to better differentiate from native methods. Thereplacemethod has been removed.- When iterating over an Object with
v-repeat, the object no longer gets a$repeaterarray. Instead, the object is now augmented with two methods:$add(key, value)and$delete(key), which will trigger corresponding view updates. - Production build now strips all warnings and debug logs. To leverage
debug: trueyou now have to use the development version. v-ifnow creates and destroys a child ViewModel instance when the binding value changes, instead of simply removing/inserting the DOM node. In addition, it can no longer be used withv-repeat. Usev-showor the new built-in array filters instead.v-withcan no longer be used alone. It now must be used with eitherv-componentorv-view.v-componentcan also be used as an empty directive just to create a child VM using the defaultVueconstructor.
Fixed
event.stopPropagation()andevent.preventDefault()insidev-onhandlers now work as expected.parentoption now works properly when used inVue.extend- Mustache bindings inside
<textarea>are now properly interpolated before being set as value.
Internal
v-component,v-withandv-ifhave been re-written for a cleaner compile flow.v-repeathas been re-written to use refined diff algorithm which triggers minimum DOM manipulations when the array is set to a different instance containing overlapping elements. This makes it efficient to pipe an Array through filters.- The compiling procedure has been further optimized and instantiation perf has increased roughly 20%.
v0.9.3
New
v-withcan now be used to bind a parent VM's data property to the child VM with a different key, e.g.v-with="childKey: parentKey". Doc here and here.- added
parentinstantiation option. This allows developer to programmatically create nested VM instances. Doc. - added new VM instance property:
$options. This can be used to access custom properties in instantiation options. Doc. - added
interpolateglobal config option. When set tofalseVue.js will skip interpolation for all mustache bindings. This is useful when there is server-rendered user content that could potentially include mustache bindings.
Changed
- when creating custom directives, the developer now need to explicitly pass in
isLiteral: true,isEmpty: trueorisFn:trueto create literal, empty or function directives.
Fixed
$indexand$keyare no longer directly attached to data objects. They are now meta properties that can only be accessed on VM instances, not the data objects themselves, since the same data object can have different$indexor$keywhen observed by different VMs.- Fixed
replace: trueoption causingcompiler.elandvm.$elto be pointing to the old, replaced element. array.splice(0)now properly empties the array in supported browsers.- When printing an object, e.g.
{{$data}}, changes inside Array elements now properly propagate out of the Array and trigger change to the object containing the Array.