vue 0.4.1 vue: ^0.4.1 copied to clipboard
Vue bindings for Dart
0.4.1 #
- Upgrade packages to work under Dart 2.1.
0.4.0 #
- Dart 2.0 is now supported!
- BREAKING CHANGE vue2 and vue2_cli have been renamed to vue and vue_cli, respectively.
- BREAKING CHANGE
package:build
is now used instead of Pub transformers. Using Pub is no longer supported. - BREAKING CHANGE Components are never globally registered. Instead, they must
explicitly be passed to the
VueComponent
annotation. - BREAKING CHANGE A new, extensible
VueAppOptions
API has been added for passing miscellaneous options to app constructors, and the specializedrouter
argument has been dropped in favor ofoptions
. - BREAKING CHANGE Mixins no longer have to be explicitly passed to the
mixins:
argument. Instead, VueDart will automatically find mixins in your class'swith
clause. - BREAKING CHANGE Mixins must now all have an
implements VueMixinRequirements
clause. This also means that they have access to pretty much the entire component/app API out-of-the-box. - BREAKING CHANGE The overridable lifecycle methods now all have a
lifecycle
prefix, e.g.void mounted
becamevoid lifecycleMounted
. - BREAKING CHANGE The constructor boilerplate has all been dropped! No more
Component(context) => super(context)
orfactory App(context) => ...
. - BREAKING CHANGE As a side-effect of the above, it is now prohibited to access
anything Vue-related in your constructors. To be precise, constructors can no longer be
used as a substitute for the created lifecycle hook. Instead, override the new
void lifecycleCreated()
method. - BREAKING CHANGE The event API has been overhauled. Instead of the vanilla Vue-style
$on
and$emit
API, it's now built around Dart-native streams and sinks. The result is far more type-safe than before. The old functions have been removed. - BREAKING CHANGE
bool
props now create a boolean prop, instead of a prop that's eithernull
or an empty string. (This is mostly a bugfix.) - BREAKING CHANGE The
vue_router
plugin now requires you pass components likeComponent()
instead of#Component
. - You can now use Sass in your styles!! Just set
lang="sass"
orlang="scss"
on your<style scoped>
tags. - Mixins are now supported on a
VueApp
. - Models are supported via
@model([event: '...'])
. - Fix methods that take optional arguments under Dart 2.0.
0.3.2 #
0.3.1 #
- Upgrade scopify to 0.2.0.
- BREAKING CHANGE Due to the above upgrade, scoped styles no longer "bleed" into child elements. This behavior can still be manually re-enabled via the bleeds option to the style element. (AFAIK no one actually really used this, so it's not really a big change.)
0.3.0 #
- BREAKING CHANGE Require explicit declaration of entry points.
- BREAKING CHANGE The
VueComponent
annotation now requires the name to be in a named argument (e.g.@VueComponent(name: 'foo')
, instead of@VueComponent('foo')
). This was necessary to support unnamed components. - Added the VueDart CLI.
- Proper error messages.
- Add VueMaterial 0.7 support.
- Add vue-router support.
- Avoid needlessly rewriting HTML source files by switching from html package's DOM manipulation to using Dart's refactoring libraries.
- Change all
vue.js
script tags tovue.min.js
when in release mode, not just unpkg ones. - Implement support for mixins (for components only for now).
- Implement scoped styles.
- Implement watchers.
- Add support for more instance methods:
$data
,$props
,$el
,$options
,$parent
,$root
,$on
,$once
,$off
,$emit
,$nextTick
,$forceUpdate
, and$destroy
. - Add
VueConfig
andVueConfig.ignoredElements
.
0.2.0 #
- Remove need for explicit initialize transformer usage.
- Upgrade initialize dependency for strong mode/DDC support.
0.1.0 #
- Initial.