updated migration guide

Author: jonasjabari

docs/2.0.0-migration-guide-wip.md

@@ -51,7 +51,7 @@ class SomeApp < Matestack::Ui::Component
 
       # new
       yield if block_given?
-    end 
+    end
   end
 
 end
@@ -69,7 +69,7 @@ class SomeApp < Matestack::Ui::App
 
       # new
       some_partial(&block)
-    end 
+    end
   end
 
   def some_partial(&block)
@@ -79,17 +79,22 @@ class SomeApp < Matestack::Ui::App
 end
 ```
 
-#### loading state element
+#### Loading state element
 
 TODO -&gt; example
 
+#### Minimal app wrapping removed
+
+- Until `1.5.0`, `matestack-ui-core` rendered a minimal app around pages without explicitly associated app
+- This behavior is removed in `2.0.0` -> a page will be rendered without any wrapping app until an app is explicitly associated
+
 ### Pages
 
 **Controller instance variables**
 
 * No more implicit controller instance variable access - &gt; inject like you would inject options into a component
 
-TODO -&gt; example 
+TODO -&gt; example
 
 ### Components
 
@@ -135,7 +140,7 @@ class Components::SomeComponent < Matestack::Ui::Component
   # Do not define any slots as optional or required
 
   def response
-    # old 
+    # old
     # slot slots[:some_slot]
 
     # new
@@ -217,9 +222,9 @@ class Components::SomeComponent < Matestack::Ui::Component
 
   # old
   # def response
-  #   plain foo 
+  #   plain foo
   #   plain options[:foo]
-  #   plain bar 
+  #   plain bar
   #   plain options[:bar]
   # end
 
@@ -246,7 +251,7 @@ class Components::SomeComponent < Matestack::Ui::Component
 
   # new
   def response
-    span class: context.bs_class 
+    span class: context.bs_class
   end
 
 end
@@ -334,7 +339,7 @@ class Components::SomeComponent < Matestack::Ui::Component
       # yield_components
       # new
       yield if block_given?
-    end 
+    end
   end
 
 end
@@ -351,7 +356,7 @@ class Components::SomeComponent < Matestack::Ui::Component
       # yield_components
       # new
       some_partial(&block)
-    end 
+    end
   end
 
   def some_partial(&block)
@@ -442,7 +447,7 @@ end
 #### Vue.js props injection/usage
 
 * No more implicit injection of all options into Vue.js component
-* No more `@component_config` instance variable and `setup` method 
+* No more `@component_config` instance variable and `setup` method
 * Use explicit method in order to inject specific options into Vue.js components
 
 TODO -&gt; change to `vue_props` as method name instead of `config`
@@ -472,7 +477,7 @@ class Components::SomeComponent < Matestack::Ui::VueJsComponent
   # end
 
   # new
-  def config
+  def vue_props
     {}.tap do |props|
       props[:foo] = options[:foo]
       props[:bar] = context.bar
@@ -491,10 +496,10 @@ Vue.component('some-component', {
     return {};
   },
   mounted: function() {
-    console.log(this.componentConfig["id"]) // undefined!
-    console.log(this.componentConfig["foo"]) // hello
-    console.log(this.componentConfig["bar"]) // world
-    console.log(this.componentConfig["baz"]) // baz
+    console.log(this.props["id"]) // undefined!
+    console.log(this.props["foo"]) // hello
+    console.log(this.props["bar"]) // world
+    console.log(this.props["baz"]) // baz
   },
 });
 ```
@@ -527,10 +532,10 @@ TODO
 ```ruby
 class SomePage < Matestack::Ui::Page
 
-  # old 
-  # include Matestack::Ui::Core::Collection::Helper
+  # old
+  # include Matestack::Ui::VueJs::Components::Collection::Helper
 
-  # new 
+  # new
   include Matestack::Ui::VueJs::Components::Collection::Helper
 
 end
@@ -543,10 +548,10 @@ end
 ```ruby
 class SomePage < Matestack::Ui::Page
 
-  # old 
-  # include Matestack::Ui::Core::Collection::Helper
+  # old
+  # include Matestack::Ui::VueJs::Components::Collection::Helper
 
-  # new 
+  # new
   include Matestack::Ui::VueJs::Components::Collection::Helper
 
   def response
@@ -582,12 +587,43 @@ end
 
 ### Onclick
 
-TODO -&gt; change to span
+* changed from rendering a `div` as root element to a `a` tag in order to have an inline root element being consistent with `transition` and `action`
+
+**this possibly breaks the appearance of your UI as we're switching from a block to an inline root element**
+
+```ruby
+onclick emit: "hello" do
+  button "Klick!"
+end
+```
+
+will now render:
+
+```html
+<a href="#" class="matestack-onclick-component-root">
+  <button>Klick!</button>
+</a>
+```
+
+instead of:
+
+```html
+<div class="matestack-onclick-component-root">
+  <button>Klick!</button>
+</div>
+```
+
+You can keep the block style by simply applying following styles to your application:
+
+```css
+.matestack-onclick-component-root{
+  display: block;
+}
+```
 
 ### Link
 
 TODO -&gt; example
 
 * link is now calling the HTML `link` tag instead of rendering an `a` tag
 * use `a href: ...` or `a path: ...` instead
-