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
Copy file name to clipboardExpand all lines: 2014/07/29/vue-next/index.html
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -329,19 +329,19 @@ <h4>Jul 29, 2014</h4>
329
329
<h2id="0-10-6"><ahref="#0-10-6" class="headerlink" title="0.10.6"></a>0.10.6</h2><p>Vue.js 0.10.6 has been released! This is another small bug-fix release and will be the last maintenance version before the next major release.</p>
330
330
<aid="more"></a>
331
331
<ul>
332
-
<li>fix <code>v-style</code> error when value is falsy or a number. ( thanks to <ahref="https://github.com/dmfilipenko" target="_blank" rel="external">@dmfilipenko</a> )</li>
333
-
<li>fix the built-in <code>currency</code> filter error when value is a string ( thanks to <ahref="https://github.com/dmfilipenko" target="_blank" rel="external">@dmfilipenko</a> )</li>
334
-
<li>fix <code>Vue.require</code> for building with Component v1.0+ ( thanks to <ahref="https://github.com/kewah" target="_blank" rel="external">@kewah</a> )</li>
335
-
<li>Allow template nodes to be passed as a template option ( thanks to <ahref="https://github.com/jordangarcia" target="_blank" rel="external">@jordangarcia</a> )</li>
332
+
<li>fix <code>v-style</code> error when value is falsy or a number. ( thanks to <ahref="https://github.com/dmfilipenko" target="_blank" rel="noopener">@dmfilipenko</a> )</li>
333
+
<li>fix the built-in <code>currency</code> filter error when value is a string ( thanks to <ahref="https://github.com/dmfilipenko" target="_blank" rel="noopener">@dmfilipenko</a> )</li>
334
+
<li>fix <code>Vue.require</code> for building with Component v1.0+ ( thanks to <ahref="https://github.com/kewah" target="_blank" rel="noopener">@kewah</a> )</li>
335
+
<li>Allow template nodes to be passed as a template option ( thanks to <ahref="https://github.com/jordangarcia" target="_blank" rel="noopener">@jordangarcia</a> )</li>
336
336
<li><code>vm.$destroy()</code> now accepts an optional argument <code>noRemove</code>. When passed in as <code>true</code> it will leave the vm’s DOM node intact after the vm is destroyed.</li>
337
337
</ul>
338
-
<h2id="Vue-next"><ahref="#Vue-next" class="headerlink" title="Vue-next"></a>Vue-next</h2><p>Some of you might have noticed there is a <ahref="https://github.com/yyx990803/vue/tree/next" target="_blank" rel="external">next</a> branch in the repo. And yes, I am re-writing Vue.js from scratch. There are two main reasons:</p>
338
+
<h2id="Vue-next"><ahref="#Vue-next" class="headerlink" title="Vue-next"></a>Vue-next</h2><p>Some of you might have noticed there is a <ahref="https://github.com/yyx990803/vue/tree/next" target="_blank" rel="noopener">next</a> branch in the repo. And yes, I am re-writing Vue.js from scratch. There are two main reasons:</p>
339
339
<ul>
340
340
<li>Fix some issues that are caused by design flaws in the current version. Because these changes affect the design of some core modules, it is actually easier to rewrite than to apply on the current codebase.</li>
341
341
<li>Improve general code quality (in particular, <code>compiler.js</code> as of now is a big pile of mess, and comments are not consistent across the codebase.)</li>
342
342
</ul>
343
-
<p>Take note that the <code>next</code> branch is still in <strong>very</strong> early stage. The internals will change a lot, and when it comes out it <strong>will</strong> break curren
1241
t applications. Despite that I will try to keep the API changes to a minimum. Major differences with current 0.10 branch are documented in <ahref="https://github.com/yyx990803/vue/blob/next/changes.md" target="_blank" rel="external"><code>changes.md</code></a>. The list is obviously incomplete and subject to change, some of them are simply ideas, but it at least gives you a taste of what to expect, and I’d appreciate your feedback on any of the topics.</p>
344
-
<p>Share your thoughts at <ahref="https://github.com/vuejs/Discussion/issues" target="_blank" rel="external">vuejs/Discussion</a>.</p>
343
+
<p>Take note that the <code>next</code> branch is still in <strong>very</strong> early stage. The internals will change a lot, and when it comes out it <strong>will</strong> break current applications. Despite that I will try to keep the API changes to a minimum. Major differences with current 0.10 branch are documented in <ahref="https://github.com/yyx990803/vue/blob/next/changes.md" target="_blank" rel="noopener"><code>changes.md</code></a>. The list is obviously incomplete and subject to change, some of them are simply ideas, but it at least gives you a taste of what to expect, and I’d appreciate your feedback on any of the topics.</p>
344
+
<p>Share your thoughts at <ahref="https://github.com/vuejs/Discussion/issues" target="_blank" rel="noopener">vuejs/Discussion</a>.</p>
Copy file name to clipboardExpand all lines: 2014/11/09/vue-011-release/index.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -326,10 +326,10 @@ <h2>
326
326
327
327
<h1>Vue.js 0.11 released!</h1>
328
328
<h4>Nov 9, 2014</h4>
329
-
<p>After the long wait, <ahref="https://github.com/yyx990803/vue/releases/tag/0.11.0" target="_blank" rel="external">Vue.js 0.11 <strong>Cowboy Bebop</strong></a> is finally here! Thanks to everyone who tried out the release candidate versions and provided feedback / bug reports along the way.</p>
329
+
<p>After the long wait, <ahref="https://github.com/yyx990803/vue/releases/tag/0.11.0" target="_blank" rel="noopener">Vue.js 0.11 <strong>Cowboy Bebop</strong></a> is finally here! Thanks to everyone who tried out the release candidate versions and provided feedback / bug reports along the way.</p>
330
330
<aid="more"></a>
331
-
<p>The 0.11 release introduced many new features and also a fair number of breaking changes, so please carefully read through the <ahref="https://github.com/yyx990803/vue/blob/master/changes.md" target="_blank" rel="external">0.11 Change List</a> before upgrading. Aside from the API changes, 0.11 also ships with better <ahref="https://codeclimate.com/github/yyx990803/vue" target="_blank" rel="external">code quality</a> and <ahref="https://coveralls.io/r/yyx990803/vue" target="_blank" rel="external">test coverage</a>, and is considerably more robust in almost every aspect.</p>
332
-
<p>This documentation site has been fully upgraded to match the new 0.11 API. For the now legacy 0.10.6 version, you can still find documentations for it at <ahref="http://legacy.vuejs.org" target="_blank" rel="external">legacy.vuejs.org</a>.</p>
331
+
<p>The 0.11 release introduced many new features and also a fair number of breaking changes, so please carefully read through the <ahref="https://github.com/yyx990803/vue/blob/master/changes.md" target="_blank" rel="noopener">0.11 Change List</a> before upgrading. Aside from the API changes, 0.11 also ships with better <ahref="https://codeclimate.com/github/yyx990803/vue" target="_blank" rel="noopener">code quality</a> and <ahref="https://coveralls.io/r/yyx990803/vue" target="_blank" rel="noopener">test coverage</a>, and is considerably more robust in almost every aspect.</p>
332
+
<p>This documentation site has been fully upgraded to match the new 0.11 API. For the now legacy 0.10.6 version, you can still find documentations for it at <ahref="http://legacy.vuejs.org" target="_blank" rel="noopener">legacy.vuejs.org</a>.</p>
Copy file name to clipboardExpand all lines: 2014/12/08/011-component/index.html
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -326,17 +326,17 @@ <h2>
326
326
327
327
<h1>0.11 Component Tips</h1>
328
328
<h4>Dec 8, 2014</h4>
329
-
<pclass="tip">Note: this post contains information for the outdated 0.11 version. Please refer to the <ahref="https://github.com/yyx990803/vue/releases" target="_blank" rel="external">0.12 release notes</a> for the changes in the API.</p>
329
+
<pclass="tip">Note: this post contains information for the outdated 0.11 version. Please refer to the <ahref="https://github.com/yyx990803/vue/releases" target="_blank" rel="noopener">0.12 release notes</a> for the changes in the API.</p>
330
330
331
-
<p>The release of 0.11 introduced <ahref="https://github.com/yyx990803/vue/blob/master/changes.md" target="_blank" rel="external">many changes</a>, but the most important one is how the new component scope works. Pre
10000
viously in 0.10.x, components have inherited scope by default. That means in a child component template you can reference parent scope properties. This often leads to tightly-coupled components, where a child component assumes knowledge of what properties are present in the parent scope. It is also possible to accidentally refer to a parent scope property in a child component.</p>
331
+
<p>The release of 0.11 introduced <ahref="https://github.com/yyx990803/vue/blob/master/changes.md" target="_blank" rel="noopener">many changes</a>, but the most important one is how the new component scope works. Previously in 0.10.x, components have inherited scope by default. That means in a child component template you can reference parent scope properties. This often leads to tightly-coupled components, where a child component assumes knowledge of what properties are present in the parent scope. It is also possible to accidentally refer to a parent scope property in a child component.</p>
332
332
<aid="more"></a>
333
333
<h3id="Isolated-Scope-and-Data-Passing"><ahref="#Isolated-Scope-and-Data-Passing" class="headerlink" title="Isolated Scope and Data Passing"></a>Isolated Scope and Data Passing</h3><p>Starting in 0.11, all child components have isolated scope by default, and the recommended way to control component data access is via <ahref="/guide/components.html#Explicit_Data_Passing">Explicit Data Passing</a> using <ahref="/api/directives.html#v-with"><code>v-with</code></a> or <ahref="/api/options.html#paramAttributes"><code>paramAttributes</code></a>.</p>
334
334
<p><code>paramAttributes</code> enables us to write Web Component style templates:</p>
<h3id="Where-Does-It-Belong"><ahref="#Where-Does-It-Belong" class="headerlink" title="Where Does It Belong?"></a>Where Does It Belong?</h3><p>Previously in 0.10, all directives on a component’s container element are compiled in the child component’s scope. Because it inherited parent scope, this worked in most situations. Starting in 0.11.1, we want to provide a cleaner separation between component scopes. The rule of thumbs is: if something appears in the parent template, it will be compiled in parent scope; if it appears in child template, it will be compiled in child scope. For example:</p>
<figureclass="highlight html"><table><tr><tdclass="code"><pre><spanclass="line"><spanclass="comment"><!-- child template, with replace: true --></span></span><br><spanclass="line"><spanclass="tag"><<spanclass="name">div</span><spanclass="attr">v-on</span>=<spanclass="string">"click:onChildClick"</span>></span></span><br><spanclass="line"><spanclass="tag"><<spanclass="name">h1</span>></span>{{childMessage}}<spanclass="tag"></<spanclass="name">h1</span>></span></span><br><spanclass="line"><spanclass="tag"><<spanclass="name">content</span>></span><spanclass="tag"></<spanclass="name">content</span>></span></span><br><spanclass="line"><spanclass="tag"></<spanclass="name">div</span>></span></span><br></pre></td></tr></table></figure>
340
340
<p>Everything in the parent template will be compiled in the parent’s scope, including the content that’s going to be inserted into the child component.</p>
341
341
<p>The only exception to the rule is <code>v-with</code> (and <code>paramAttributes</code> which compiles down to <code>v-with</code>), which works in both places - so you don’t need to worry about it too much.</p>
342
342
<h3id="Cleaner-Event-Communication"><ahref="#Cleaner-Event-Communication" class="headerlink" title="Cleaner Event Communication"></a>Cleaner Event Communication</h3><p>Previously the standard way for a child component to communicate to its parent is via dispatching events. However, with this approach, the event listeners on the parent component are not guaranteed to be listening on the desired child component only. It’s also possible to trigger undesired listeners further up the chain if we do not cancel the event.</p>
0 commit comments