Skip to content

Commit 28dadcf

Browse files
committed
chore: update changelog
1 parent 5190e3e commit 28dadcf

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

CHANGELOG.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,26 @@
1+
<a name="2.5.0-alpha.0"></a>
2+
# [2.5.0-alpha.0](https://github.com/nativescript-vue/nativescript-vue/compare/v2.4.0...v2.5.0-alpha.0) (2019-08-24)
3+
4+
5+
### Bug Fixes
6+
7+
* **devtools:** refresh devtools when state changes ([4d28b34](https://github.com/nativescript-vue/nativescript-vue/commit/4d28b34))
8+
* crash on blank .vue template section ([0295650](https://github.com/nativescript-vue/nativescript-vue/commit/0295650))
9+
10+
11+
### Features
12+
13+
* **devtools:** show navigation entries under Frame ([e82d067](https://github.com/nativescript-vue/nativescript-vue/commit/e82d067))
14+
15+
16+
### BREAKING CHANGES
17+
18+
* **devtools:** A Frame now only accepts a single child element, that is the defaultPage for the Frame. If you have multiple pages nested under the Frame element, you will need to refactor to use `$navigateTo` instead. Additionally the default slot is only rendered once, meaning that it will not be reactive after the initial render. This is due to how the Frame element works, it renders the defaultPage, and then "navigates" to it, and it is no longer a direct child of the Frame and cannot be reactive. If this affects you, plese open an issue and describe your use case, so we can discuss possible solutions.
19+
20+
For most users this will not requre any additional refactoring.
21+
22+
23+
124
<a name="2.4.0"></a>
225
# [2.4.0](https://github.com/nativescript-vue/nativescript-vue/compare/v2.4.0-alpha.0...v2.4.0) (2019-07-23)
326

0 commit comments

Comments
 (0)