Releases: nativescript-vue/nativescript-vue
Releases · nativescript-vue/nativescript-vue
v2.6.0
2.6.0 (2020-04-13)
Bug Fixes
- remove console.log override (#627) (226e108)
- renderer: check for undefined before trimming style (#622) (9ce38a0)
Features
- resolve navigation page on navigation event (#624) (787d1a5)
- logging: log node creation errors (#625) (b502fc8)
- registry: allow overriding elements (#626) (e37788c)
BREAKING CHANGES
- Our
console.log
override usingutil-inspect
has been removed due to performance concerns. If you were usingVue.config.debug = true
to get colorful console.logs, this will no longer work. We have documented how you may add this feature back to your app if you relied on this behavior. See CONSOLE_LOG_OVERRIDE.md for details.
v2.5.1
v2.5.0
v2.5.0-alpha.3
v2.5.0-alpha.2
v2.5.0-alpha.1
v2.5.0-alpha.0
2.5.0-alpha.0 (2019-08-24)
Bug Fixes
- devtools: refresh devtools when state changes (4d28b34)
- crash on blank .vue template section (0295650)
Features
- devtools: show navigation entries under Frame (e82d067)
BREAKING CHANGES
- 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.
For most users this will not requre any additional refactoring.