New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0 csp #6995
1.0 csp #6995
Conversation
fix: directive I/F consistency
- No need to merge props into the data object. they should just be defined as reactive properties on the vm instance. - They should not observe the value when set. They should already be reactive if needed.
update internal explain comments
Support the followings: - Directive instance properties: `arg`, `modifiers` - Priority for terminal directive BREAKING CHANGES: - API: Change internal `terminalDirectives` array to `terminal: true` directive options
Improve terminalable directive
There will still be new releases for 1.x. And we will try to backport some useful features. It's just the current focus is getting 2.0 shipped first.
Is it possible for this to be under a 1.0.x release or something similar? I see that further releases on the 1.x have been halted looking forward to v2 (yay!) but some backward compatible changes might be awesome to have.
* fix broken todomvc test * bump casperjs
my tests that were using nextTick
started failing since updating to 1.0.27...
@broox a fix is already implemented, publishing soon.
I tried rc7, and i feel that old timerFunc was much more responsive then new.
* fix directive sort compare * fix directive sort compare. and update normal directives test case.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
The text was updated successfully, but these errors were encountered: