You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vue 0.12 had a different behavior when instanciating components, it wasn't replacing the root element.
When migrating to Vue 1.x, we had to toggle Vue.config.replace = false in order to maintain a compatibility with some component.
This setting setting is deprecated and then removed in Vue 2.0.
Context
In order to stay close to standard Vue.js behavior, to allow upgrade and to simplify component styling (the component will be exactly as written, no custom surronding element), we need to drop Vue.config.replace = false and fix components for this behavior.
The text was updated successfully, but these errors were encountered:
noirbizarre
changed the title
Make all components to work without Vue.config.replace = false
Make all components to work without Vue.config.replace = false
Feb 15, 2017
Detailed Description
Vue 0.12 had a different behavior when instanciating components, it wasn't replacing the root element.
When migrating to Vue 1.x, we had to toggle
Vue.config.replace = false
in order to maintain a compatibility with some component.This setting setting is deprecated and then removed in Vue 2.0.
Context
In order to stay close to standard Vue.js behavior, to allow upgrade and to simplify component styling (the component will be exactly as written, no custom surronding element), we need to drop
Vue.config.replace = false
and fix components for this behavior.The text was updated successfully, but these errors were encountered: