From a821ed482cd911468e67f745ba155742b80b595a Mon Sep 17 00:00:00 2001 From: kazuya kawaguchi Date: Sat, 13 May 2017 00:43:12 +0900 Subject: [PATCH 0001/1339] fix invalid template NOTE: feedback from https://github.com/vuejs/jp.vuejs.org/pull/256 --- src/v2/guide/class-and-style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/class-and-style.md b/src/v2/guide/class-and-style.md index 493d18b0d4..cae01de6b9 100644 --- a/src/v2/guide/class-and-style.md +++ b/src/v2/guide/class-and-style.md @@ -200,5 +200,5 @@ When you use a CSS property that requires [vendor prefixes](https://developer.mo Starting in 2.3 you can provide an array of multiple (prefixed) values to a style property, for example: ``` html -
+
``` From 1d0a3968fd24f7abc984270d09454c3a8336aefd Mon Sep 17 00:00:00 2001 From: Paul Verbeek-Mast Date: Tue, 16 May 2017 07:24:08 +0200 Subject: [PATCH 0002/1339] added v-bind to example (#907) Added `v-bind` to the Multiple Values example for consistency --- src/v2/guide/class-and-style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/class-and-style.md b/src/v2/guide/class-and-style.md index cae01de6b9..2f04daff74 100644 --- a/src/v2/guide/class-and-style.md +++ b/src/v2/guide/class-and-style.md @@ -200,5 +200,5 @@ When you use a CSS property that requires [vendor prefixes](https://developer.mo Starting in 2.3 you can provide an array of multiple (prefixed) values to a style property, for example: ``` html -
+
``` From 9bc8cfcfc459229e6c13ce3591937239dca2cd8b Mon Sep 17 00:00:00 2001 From: Philip Belesky Date: Tue, 16 May 2017 15:24:45 +1000 Subject: [PATCH 0003/1339] Fix minor typos in comparison.md (#906) --- src/v2/guide/comparison.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/v2/guide/comparison.md b/src/v2/guide/comparison.md index ad964f883d..39f7ed75ae 100644 --- a/src/v2/guide/comparison.md +++ b/src/v2/guide/comparison.md @@ -26,7 +26,7 @@ The React community [has been instrumental](https://github.com/vuejs/vuejs.org/i ### Performance -Both React and Vue offer comparable performance in most commonly seen use cases, with Vue usually slightly head due to its lighter-weight Virtual DOM implementation. If you are interested in numbers, you can check out this [3rd party benchmark](https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts/table.html) which focuses on raw rendering/updating performance. Note that this does not take complex component structures into account, so should only be considered a reference rather than a verdict. +Both React and Vue offer comparable performance in most commonly seen use cases, with Vue usually slightly ahead due to its lighter-weight Virtual DOM implementation. If you are interested in numbers, you can check out this [3rd party benchmark](https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts/table.html) which focuses on raw rendering/updating performance. Note that this does not take complex component structures into account, so should only be considered a reference rather than a verdict. #### Optimization Efforts @@ -62,7 +62,7 @@ In Vue, we also have [render functions](render-function.html) and even [support - You can even use pre-processors such as Pug (formerly known as Jade) to author your Vue templates. -Some argue that you'd need to learn an extra DSL (Domain-Specific Language) to be able to write templates - we believe this difference is superficial at best. First, JSX doesn't mean the user don't need to learn anything - it's additional syntax on top of plain JavaScript, so it's easy for anyone familar with JavaScript to learn, but saying it's essentially free is misleading. Similarly, template is just additional syntax on top of plain HTML and thus has very low learning cost for those who are already familiar with HTML. With the DSL we are also able to help the user get more done with less code (e.g. `v-on` modifiers). The same task can involve a lot more code when using plain JSX or render functions. +Some argue that you'd need to learn an extra DSL (Domain-Specific Language) to be able to write templates - we believe this difference is superficial at best. First, JSX doesn't mean the user don't need to learn anything - it's additional syntax on top of plain JavaScript, so it's easy for anyone familiar with JavaScript to learn, but saying it's essentially free is misleading. Similarly, template is just additional syntax on top of plain HTML and thus has very low learning cost for those who are already familiar with HTML. With the DSL we are also able to help the user get more done with less code (e.g. `v-on` modifiers). The same task can involve a lot more code when using plain JSX or render functions. On a higher level, we can divide components into two categories: presentational ones and logical ones. We recommend using templates for presentational components and render function / JSX for logical ones. The percentage of these components depends on the type of app you are building, but in general we find presentational ones to be much more common. From 5d6681e0ffb9ca92cfe85f59183deefe8bfdde2e Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Tue, 16 May 2017 07:27:51 +0200 Subject: [PATCH 0004/1339] Angular 1 to AngularJS and Angular 2 to Angular (#908) Signed-off-by: Bruno Lesieur --- src/v2/guide/comparison.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/src/v2/guide/comparison.md b/src/v2/guide/comparison.md index 39f7ed75ae..462e420ce2 100644 --- a/src/v2/guide/comparison.md +++ b/src/v2/guide/comparison.md @@ -96,7 +96,7 @@ For large applications, both Vue and React offer robust routing solutions. The R Another important difference between these offerings is that Vue's companion libraries for state management and routing (among [other concerns](https://github.com/vuejs)) are all officially supported and kept up-to-date with the core library. React instead chooses to leave these concerns to the community, creating a more fragmented ecosystem. Being more popular though, React's ecosystem is considerably richer than Vue's. -Finally, Vue offers a [CLI project generator](https://github.com/vuejs/vue-cli) that makes it trivially easy to start a new project using your choice of build system, including [Webpack](https://github.com/vuejs-templates/webpack), [Browserify](https://github.com/vuejs-templates/browserify), or even [no build system](https://github.com/vuejs-templates/simple). React is also making strides in this area with [create-react-app](https://github.com/facebookincubator/create-react-app), but it currently has a few limitations: +Finally, Vue offers a [CLI project generator](https://github.com/vuejs/vue-cli) that makes it trivially easy to start a new project using your choice of build system, including [webpack](https://github.com/vuejs-templates/webpack), [Browserify](https://github.com/vuejs-templates/browserify), or even [no build system](https://github.com/vuejs-templates/simple). React is also making strides in this area with [create-react-app](https://github.com/facebookincubator/create-react-app), but it currently has a few limitations: - It does not allow any configuration during project generation, while Vue's project templates allow [Yeoman](http://yeoman.io/)-like customization. - It only offers a single template that assumes you're building a single-page application, while Vue offers a wide variety of templates for various purposes and build systems. @@ -130,37 +130,37 @@ MobX has become quite popular in the React community and it actually uses a near ## AngularJS (Angular 1) -Some of Vue's syntax will look very similar to Angular (e.g. `v-if` vs `ng-if`). This is because there were a lot of things that Angular got right and these were an inspiration for Vue very early in its development. There are also many pains that come with Angular however, where Vue has attempted to offer a significant improvement. +Some of Vue's syntax will look very similar to AngularJS (e.g. `v-if` vs `ng-if`). This is because there were a lot of things that AngularJS got right and these were an inspiration for Vue very early in its development. There are also many pains that come with AngularJS however, where Vue has attempted to offer a significant improvement. ### Complexity -Vue is much simpler than Angular 1, both in terms of API and design. Learning enough to build non-trivial applications typically takes less than a day, which is not true for Angular 1. +Vue is much simpler than AngularJS, both in terms of API and design. Learning enough to build non-trivial applications typically takes less than a day, which is not true for AngularJS. ### Flexibility and Modularity -Angular 1 has strong opinions about how your applications should be structured, while Vue is a more flexible, modular solution. While this makes Vue more adaptable to a wide variety of projects, we also recognize that sometimes it's useful to have some decisions made for you, so that you can just get started coding. +AngularJS has strong opinions about how your applications should be structured, while Vue is a more flexible, modular solution. While this makes Vue more adaptable to a wide variety of projects, we also recognize that sometimes it's useful to have some decisions made for you, so that you can just get started coding. -That's why we offer a [Webpack template](https://github.com/vuejs-templates/webpack) that can set you up within minutes, while also granting you access to advanced features such as hot module reloading, linting, CSS extraction, and much more. +That's why we offer a [webpack template](https://github.com/vuejs-templates/webpack) that can set you up within minutes, while also granting you access to advanced features such as hot module reloading, linting, CSS extraction, and much more. ### Data binding -Angular 1 uses two-way binding between scopes, while Vue enforces a one-way data flow between components. This makes the flow of data easier to reason about in non-trivial applications. +AngularJS uses two-way binding between scopes, while Vue enforces a one-way data flow between components. This makes the flow of data easier to reason about in non-trivial applications. ### Directives vs Components -Vue has a clearer separation between directives and components. Directives are meant to encapsulate DOM manipulations only, while components are self-contained units that have their own view and data logic. In Angular, there's a lot of confusion between the two. +Vue has a clearer separation between directives and components. Directives are meant to encapsulate DOM manipulations only, while components are self-contained units that have their own view and data logic. In AngularJS, there's a lot of confusion between the two. ### Performance -Vue has better performance and is much, much easier to optimize because it doesn't use dirty checking. Angular 1 becomes slow when there are a lot of watchers, because every time anything in the scope changes, all these watchers need to be re-evaluated again. Also, the digest cycle may have to run multiple times to "stabilize" if some watcher triggers another update. Angular users often have to resort to esoteric techniques to get around the digest cycle, and in some situations, there's simply no way to optimize a scope with many watchers. +Vue has better performance and is much, much easier to optimize because it doesn't use dirty checking. AngularJS becomes slow when there are a lot of watchers, because every time anything in the scope changes, all these watchers need to be re-evaluated again. Also, the digest cycle may have to run multiple times to "stabilize" if some watcher triggers another update. AngularJS users often have to resort to esoteric techniques to get around the digest cycle, and in some situations, there's simply no way to optimize a scope with many watchers. Vue doesn't suffer from this at all because it uses a transparent dependency-tracking observation system with async queueing - all changes trigger independently unless they have explicit dependency relationships. -Interestingly, there are quite a few similarities in how Angular 2 and Vue are addressing these Angular 1 issues. +Interestingly, there are quite a few similarities in how Angular and Vue are addressing these AngularJS issues. ## Angular (Formerly known as Angular 2) -We have a separate section for the new Angular because it really is a completely different framework from Angular 1. For example, it features a first-class component system, many implementation details have been completely rewritten, and the API has also changed quite drastically. +We have a separate section for the new Angular because it really is a completely different framework from AngularJS. For example, it features a first-class component system, many implementation details have been completely rewritten, and the API has also changed quite drastically. ### TypeScript @@ -172,13 +172,13 @@ Finally, although not as deeply integrated with TypeScript as Angular is, Vue al ### Size and Performance -In terms of performance, both frameworks are exceptionally fast and there isn't enough data from real world use cases to make a verdict. However if you are determined to see some numbers, Vue 2.0 seems to be ahead of Angular 2 according to this [3rd party benchmark](http://stefankrause.net/js-frameworks-benchmark4/webdriver-ts/table.html). +In terms of performance, both frameworks are exceptionally fast and there isn't enough data from real world use cases to make a verdict. However if you are determined to see some numbers, Vue 2.0 seems to be ahead of Angular according to this [3rd party benchmark](http://stefankrause.net/js-frameworks-benchmark4/webdriver-ts/table.html). Recent versions of Angular, with AOT compilation and tree-shaking, have been able to get its size down considerably. However, a full-featured Vue 2 project with Vuex + vue-router included (~30kb gzipped) is still significantly lighter than an out-of-the-box, AOT-compiled application generated by `angular-cli` (~130kb gzipped). ### Flexibility -Vue is much less opinionated than Angular 2, offering official support for a variety of build systems, with no restrictions on how you structure your application. Many developers enjoy this freedom, while some prefer having only one Right Way to build any application. +Vue is much less opinionated than Angular, offering official support for a variety of build systems, with no restrictions on how you structure your application. Many developers enjoy this freedom, while some prefer having only one Right Way to build any application. ### Learning Curve @@ -214,7 +214,7 @@ In Polymer 1.0, the team has also made its data-binding system very limited in o Polymer custom elements are authored in HTML files, which limits you to plain JavaScript/CSS (and language features supported by today's browsers). In comparison, Vue's single file components allows you to easily use ES2015+ and any CSS preprocessors you want. -When deploying to production, Polymer recommends loading everything on-the-fly with HTML Imports, which assumes browsers implementing the spec, and HTTP/2 support on both server and client. This may or may not be feasible depending on your target audience and deployment environment. In cases where this is not desirable, you will have to use a special tool called Vulcanizer to bundle your Polymer elements. On this front, Vue can combine its async component feature with Webpack's code-splitting feature to easily split out parts of the application bundle to be lazy-loaded. This ensures compatibility with older browsers while retaining great app loading performance. +When deploying to production, Polymer recommends loading everything on-the-fly with HTML Imports, which assumes browsers implementing the spec, and HTTP/2 support on both server and client. This may or may not be feasible depending on your target audience and deployment environment. In cases where this is not desirable, you will have to use a special tool called Vulcanizer to bundle your Polymer elements. On this front, Vue can combine its async component feature with webpack's code-splitting feature to easily split out parts of the application bundle to be lazy-loaded. This ensures compatibility with older browsers while retaining great app loading performance. It is also totally feasible to offer deeper integration between Vue with Web Component specs such as Custom Elements and Shadow DOM style encapsulation - however at this moment we are still waiting for the specs to mature and be widely implemented in all mainstream browsers before making any serious commitments. @@ -224,5 +224,5 @@ Riot 2.0 provides a similar component-based development model (which is called a - [Transition effect system](transitions.html). Riot has none. - A far more powerful router. Riot’s routing API is extremely minimal. -- Better performance. Riot [traverses a DOM tree](http://riotjs.com/compare/#virtual-dom-vs-expressions-binding) rather than using a virtual DOM, so suffers from the same performance issues as Angular 1. -- More mature tooling support. Vue provides official support for [Webpack](https://github.com/vuejs/vue-loader) and [Browserify](https://github.com/vuejs/vueify), while Riot relies on community support for build system integration. +- Better performance. Riot [traverses a DOM tree](http://riotjs.com/compare/#virtual-dom-vs-expressions-binding) rather than using a virtual DOM, so suffers from the same performance issues as AngularJS. +- More mature tooling support. Vue provides official support for [webpack](https://github.com/vuejs/vue-loader) and [Browserify](https://github.com/vuejs/vueify), while Riot relies on community support for build system integration. From 8ca28376ed5ed13acde6c7cb96f93ecd1492bbce Mon Sep 17 00:00:00 2001 From: Paul Verbeek-Mast Date: Tue, 16 May 2017 09:27:34 +0200 Subject: [PATCH 0005/1339] Added explanation for rendering of multiple values (#909) --- src/v2/guide/class-and-style.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/v2/guide/class-and-style.md b/src/v2/guide/class-and-style.md index 2f04daff74..9554c81f63 100644 --- a/src/v2/guide/class-and-style.md +++ b/src/v2/guide/class-and-style.md @@ -202,3 +202,5 @@ Starting in 2.3 you can provide an array of multiple (prefixed) values to a styl ``` html
``` + +This will only render the last value in the array which the browser supports. In this example, it will render `display: flex` for browsers that support the unprefixed version of flexbox. From 8efaae390aa234f0e1a3fa9cb781aac28b3de7a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ant=C3=A9rio=20Vieira?= Date: Tue, 16 May 2017 12:04:07 -0300 Subject: [PATCH 0006/1339] =?UTF-8?q?Add=20reference=20for=20Portugu=C3=AA?= =?UTF-8?q?s-Br=20translation=20(#910)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 36 +++++++++++++++++++++--------------- 1 file changed, 21 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index eb016681d6..34ea444214 100644 --- a/README.md +++ b/README.md @@ -16,9 +16,15 @@ $ hexo server Translation for this documentation project are currently mantained in separate repositories forked from this original one. -### Mandarin +### French -* Translation Repo - [/vuejs/cn.vuejs.org](https://github.com/vuejs/cn.vuejs.org) +French translation is maintained by Vuejs-FR. + +* Translation Repo — [/vuejs-fr/vuejs.org](https://github.com/vuejs-fr/vuejs.org) + +### Italian + +* Translation Repo - [/vuejs/it.vuejs.org](https://github.com/vuejs/it.vuejs.org) ### Japanese @@ -27,29 +33,29 @@ Japanese translation is maintained by [Vue.js japan user group](https://github.c * Translation Repo - [/vuejs/jp.vuejs.org](https://github.com/vuejs/jp.vuejs.org) * Primary maintainer - [kazupon](https://github.com/kazupon) -### Russian +### Korean -Russian translation is maintained by Translation Gang. +Korean translation is maintained by [Vue.js Korean User group](https://github.com/vuejs-kr). -* Translation Repo — [/translation-gang/ru.vuejs.org](https://github.com/translation-gang/ru.vuejs.org) -* Primary maintainer - [Grigoriy Beziuk](https://gbezyuk.github.io) +* Translation Repo - [/vuejs-kr/kr.vuejs.org](https://github.com/vuejs-kr/kr.vuejs.org) +* Primary maintainer - [ChangJoo Park](https://github.com/ChangJoo-Park) -### Italian +### Mandarin -* Translation Repo - [/vuejs/it.vuejs.org](https://github.com/vuejs/it.vuejs.org) +* Translation Repo - [/vuejs/cn.vuejs.org](https://github.com/vuejs/cn.vuejs.org) -### Korean +### Português-Br -Korean translation is maintained by [Vue.js Korean User group](https://github.com/vuejs-kr). +Português-Br translation is maintained by [Vuejs-Br](https://github.com/vuejs-br). -* Translation Repo - [/vuejs-kr/kr.vuejs.org](https://github.com/vuejs-kr/kr.vuejs.org) -* Primary maintainer - [ChangJoo Park](https://github.com/ChangJoo-Park) +* Translation Repo - [/vuejs-br/br.vuejs.org](https://github.com/vuejs-br/br.vuejs.org) -### French +### Russian -French translation is maintained by Vuejs-FR. +Russian translation is maintained by Translation Gang. -* Translation Repo — [/vuejs-fr/vuejs.org](https://github.com/vuejs-fr/vuejs.org) +* Translation Repo — [/translation-gang/ru.vuejs.org](https://github.com/translation-gang/ru.vuejs.org) +* Primary maintainer - [Grigoriy Beziuk](https://gbezyuk.github.io) ### Want to help with the translation? From 75b7dea1b9302421e96377def82314fc4d269184 Mon Sep 17 00:00:00 2001 From: Chris Fritz Date: Thu, 18 May 2017 14:51:47 -0400 Subject: [PATCH 0007/1339] add link to benchmark for ember performance comparison --- package.json | 2 +- src/v2/guide/comparison.md | 2 +- yarn.lock | 6 +----- 3 files changed, 3 insertions(+), 7 deletions(-) diff --git a/package.json b/package.json index a38307d809..be1d5d5748 100644 --- a/package.json +++ b/package.json @@ -19,4 +19,4 @@ "hexo-renderer-stylus": "^0.3.1", "hexo-server": "^0.2.0" } -} +} \ No newline at end of file diff --git a/src/v2/guide/comparison.md b/src/v2/guide/comparison.md index 462e420ce2..63383da169 100644 --- a/src/v2/guide/comparison.md +++ b/src/v2/guide/comparison.md @@ -196,7 +196,7 @@ That said, it would probably make a better comparison between Vue core and Ember - Vue's template syntax harnesses the full power of JavaScript expressions, while Handlebars' expression and helper syntax is intentionally quite limited in comparison. -- Performance-wise, Vue outperforms Ember by a fair margin, even after the latest Glimmer engine update in Ember 2.0. Vue automatically batches updates, while in Ember you need to manually manage run loops in performance-critical situations. +- Performance-wise, Vue outperforms Ember [by a fair margin](https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts/table.html), even after the latest Glimmer engine update in Ember 2.x. Vue automatically batches updates, while in Ember you need to manually manage run loops in performance-critical situations. ## Knockout diff --git a/yarn.lock b/yarn.lock index 98758bc9d7..687486ddc4 100644 --- a/yarn.lock +++ b/yarn.lock @@ -1285,11 +1285,7 @@ moment-timezone@^0.5.4: dependencies: moment ">= 2.6.0" -"moment@>= 2.6.0", moment@^2.10.6, moment@^2.11.2: - version "2.15.2" - resolved "https://registry.yarnpkg.com/moment/-/moment-2.15.2.tgz#1bfdedf6a6e345f322fe956d5df5bd08a8ce84dc" - -moment@~2.13.0: +"moment@>= 2.6.0", moment@^2.10.6, moment@^2.11.2, moment@~2.13.0: version "2.13.0" resolved "https://registry.yarnpkg.com/moment/-/moment-2.13.0.tgz#24162d99521e6d40f99ae6939e806d2139eaac52" From 382b8acb61db17dedeebf8303604ecc0a7256f76 Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Fri, 19 May 2017 02:35:08 +0200 Subject: [PATCH 0008/1339] Open mobile memu only if slide come from left-border side of screen (#913) Signed-off-by: Bruno Lesieur --- themes/vue/source/js/common.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/themes/vue/source/js/common.js b/themes/vue/source/js/common.js index 293417999f..0ab2299feb 100644 --- a/themes/vue/source/js/common.js +++ b/themes/vue/source/js/common.js @@ -126,7 +126,7 @@ var yDiff = end.y - start.y if (Math.abs(xDiff) > Math.abs(yDiff)) { - if (xDiff > 0) sidebar.classList.add('open') + if (xDiff > 0 && start.x <= 80) sidebar.classList.add('open') else sidebar.classList.remove('open') } }) From 84a65b1001d5927fabd41f695c3fd276c7dca107 Mon Sep 17 00:00:00 2001 From: David Lloyd Date: Thu, 18 May 2017 20:40:28 -0400 Subject: [PATCH 0009/1339] Clarify v-html usage (#905) * Update syntax.md Originally, I'd thought that: ```
This {{ some_html}}
``` (where we might have `vm.data.some_html='hello'`) ... would render something like: **hello** But instead we get: ``` Property or method "rawHtml" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. ``` ...if one is watching console errors. My wording could be a little bit kludgy and others might be able to make it clearer but I think this may overcome some misunderstandings for those not familiar with vuejs. * Update syntax.md --- src/v2/guide/syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/syntax.md b/src/v2/guide/syntax.md index 5cb1464fd5..9b4367c009 100644 --- a/src/v2/guide/syntax.md +++ b/src/v2/guide/syntax.md @@ -36,7 +36,7 @@ The double mustaches interprets the data as plain text, not HTML. In order to ou
``` -The contents are inserted as plain HTML - data bindings are ignored. Note that you cannot use `v-html` to compose template partials, because Vue is not a string-based templating engine. Instead, components are preferred as the fundamental unit for UI reuse and composition. +The contents of this `div` will be replaced with the value of the `rawHtml` property, interpreted as plain HTML - data bindings are ignored. Note that you cannot use `v-html` to compose template partials, because Vue is not a string-based templating engine. Instead, components are preferred as the fundamental unit for UI reuse and composition.

Dynamically rendering arbitrary HTML on your website can be very dangerous because it can easily lead to [XSS vulnerabilities](https://en.wikipedia.org/wiki/Cross-site_scripting). Only use HTML interpolation on trusted content and **never** on user-provided content.

From ea5356a69a8bcc2243f983a0d911c9abd68a7e6c Mon Sep 17 00:00:00 2001 From: Etienne Levesque Guitard Date: Thu, 18 May 2017 20:43:40 -0400 Subject: [PATCH 0010/1339] Align Range v-for HTML sample with actual result (#904) --- src/v2/guide/list.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/list.md b/src/v2/guide/list.md index ad65a9d43e..133d9047ea 100644 --- a/src/v2/guide/list.md +++ b/src/v2/guide/list.md @@ -196,7 +196,7 @@ And another for the index: ``` html
- {{ n }} + {{ n }}
``` From a5b1643f85e46ef801d500b051cf81183e472f60 Mon Sep 17 00:00:00 2001 From: Bruno Lesieur Date: Fri, 19 May 2017 02:50:35 +0200 Subject: [PATCH 0011/1339] `component.md` : Component Naming Conventions better consistency (#903) * Add french translation link Signed-off-by: Bruno Lesieur * kebab-case explaination updates Signed-off-by: Bruno Lesieur * kebab-case to kebab-cased Signed-off-by: Bruno Lesieur * Remove space before self-closing component --- src/v2/guide/components.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/v2/guide/components.md b/src/v2/guide/components.md index 841eee6f98..c544bbfdaa 100644 --- a/src/v2/guide/components.md +++ b/src/v2/guide/components.md @@ -1155,25 +1155,25 @@ When using _string_ templates however, we're not bound by HTML's case-insensitiv - kebab-case - camelCase or kebab-case if the component has been defined using camelCase -- kebab-case, camelCase or Title case if the component has been defined using TitleCase +- kebab-case, camelCase or TitleCase if the component has been defined using TitleCase ``` js components: { - 'kebab-case-component': { /* ... */ }, - camelCaseComponent: { /* ... */ }, - TitleCaseComponent: { /* ... */ } + 'kebab-cased-component': { /* ... */ }, + camelCasedComponent: { /* ... */ }, + TitleCasedComponent: { /* ... */ } } ``` ``` html - + - - + + - - - + + + ``` This means that the TitleCase is the most universal _declaration convention_ and kebab-case is the most universal _usage convention_. From 8c545d35ffb5fcf3111879b3d72b7e3421e1db6a Mon Sep 17 00:00:00 2001 From: Andreas Solleder Date: Sat, 20 May 2017 10:38:54 +0200 Subject: [PATCH 0012/1339] fix: typos using misspell (#916) This PR is part of a campaign to fix a lot of typos on github! You can see the progress on https://github.com/fixTypos/fix_typos/ https://github.com/client9/misspell --- README.md | 2 +- src/_posts/011-component.md | 2 +- src/_posts/vue-next.md | 4 ++-- src/v2/guide/migration-vuex.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 34ea444214..651c5e2a3a 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ $ hexo server ## On Translations -Translation for this documentation project are currently mantained in separate repositories forked from this original one. +Translation for this documentation project are currently maintained in separate repositories forked from this original one. ### French diff --git a/src/_posts/011-component.md b/src/_posts/011-component.md index 2be314f1ac..c95230e530 100644 --- a/src/_posts/011-component.md +++ b/src/_posts/011-component.md @@ -54,7 +54,7 @@ The only exception to the rule is `v-with` (and `paramAttributes` which compiles ### Cleaner Event Communication -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 listners further up the chain if we do not cancel the event. +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. The most common use case is for a parent to react to the events from a specific, direct child component. So in 0.11.4, [a new directive `v-events`](/api/directives.html#v-events) has been introduced to enable exactly this behavior. diff --git a/src/_posts/vue-next.md b/src/_posts/vue-next.md index f30cd9c625..fe324b223d 100644 --- a/src/_posts/vue-next.md +++ b/src/_posts/vue-next.md @@ -5,7 +5,7 @@ date: 2014-07-29 00:04:55 ## 0.10.6 -Vue.js 0.10.6 has been released! This is another small bug-fix release and will be the last maintainance version before the next major release. +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. @@ -22,6 +22,6 @@ Some of you might have noticed there is a [next](https://github.com/yyx990803/vu - 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. - Improve general code quality (in particular, `compiler.js` as of now is a big pile of mess, and comments are not consistent across the codebase.) -Take note that the `next` branch is still in **very** early stage. The internals will change a lot, and when it comes out it **will** 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 [`changes.md`](https://github.com/yyx990803/vue/blob/next/changes.md). 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 appreicate your feedback on any of the topics. +Take note that the `next` branch is still in **very** early stage. The internals will change a lot, and when it comes out it **will** 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 [`changes.md`](https://github.com/yyx990803/vue/blob/next/changes.md). 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. Share your thoughts at [vuejs/Discussion](https://github.com/vuejs/Discussion/issues). diff --git a/src/v2/guide/migration-vuex.md b/src/v2/guide/migration-vuex.md index 1e5aa28bdf..f15e6f0667 100644 --- a/src/v2/guide/migration-vuex.md +++ b/src/v2/guide/migration-vuex.md @@ -9,7 +9,7 @@ order: 28 Both Vuex 1.0 and 2.0: - fully support both Vue 1.0 and 2.0 -- will be maintained for the forseeable future +- will be maintained for the foreseeable future They have slightly different target users however. From cbd34422addcf0abe0595081fb1e4f22b9e9dc06 Mon Sep 17 00:00:00 2001 From: Daniel Bushman Date: Sat, 20 May 2017 02:41:06 -0600 Subject: [PATCH 0013/1339] fixed favicon's MIME type (#915) --- themes/vue/layout/layout.ejs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/themes/vue/layout/layout.ejs b/themes/vue/layout/layout.ejs index 7be91e1506..bdb3ef70b7 100644 --- a/themes/vue/layout/layout.ejs +++ b/themes/vue/layout/layout.ejs @@ -17,7 +17,7 @@ - " type="image/x-icon"> + " type="image/png"> From 58c9239dc4cb7839da46e7f9711213bdb15f6e59 Mon Sep 17 00:00:00 2001 From: Brian Juul Andersen Date: Sat, 20 May 2017 16:16:57 +0200 Subject: [PATCH 0014/1339] Fixed minor grammatical error. (#914) Fixed minor grammatical error. --- src/v2/guide/comparison.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/comparison.md b/src/v2/guide/comparison.md index 63383da169..1b22f7b0f7 100644 --- a/src/v2/guide/comparison.md +++ b/src/v2/guide/comparison.md @@ -184,7 +184,7 @@ Vue is much less opinionated than Angular, offering official support for a varie To get started with Vue, all you need is familiarity with HTML and ES5 JavaScript (i.e. plain JavaScript). With these basic skills, you can start building non-trivial applications within less than a day of reading [the guide](./). -Angular's learning curve is much steeper. The API surface of the framework is simply huge and the user will need to familiarize yourself with a lot more concepts before getting productive. Obviously, the complexity of Angular is largely due to its design goal of targeting only large, complex applications - but that does make the framework a lot more difficult for less-experienced developers to pick up. +Angular's learning curve is much steeper. The API surface of the framework is simply huge and as a user you will need to familiarize yourself with a lot more concepts before getting productive. Obviously, the complexity of Angular is largely due to its design goal of targeting only large, complex applications - but that does make the framework a lot more difficult for less-experienced developers to pick up. ## Ember From 8ee417b98d59f4611361f03b1c9a042b96f3b51b Mon Sep 17 00:00:00 2001 From: Chris Fritz Date: Sat, 20 May 2017 11:34:36 -0400 Subject: [PATCH 0015/1339] make template compilation results selectable --- src/v2/guide/render-function.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/v2/guide/render-function.md b/src/v2/guide/render-function.md index 692883bba4..43accc7266 100644 --- a/src/v2/guide/render-function.md +++ b/src/v2/guide/render-function.md @@ -605,6 +605,10 @@ console.error = function (error) { } + + + +
+
+

The Core Team

+ +

+ The development of Vue and its ecosystem is guided by an international team, + some of whom have chosen to be featured below. +

+ + +
+ +
+

Community Partners

+ +

+ Some members of the Vue community have so enriched it, that they deserve special mention. + We've developed a more intimate relationship with these key partners, often coordinating + with them on upcoming news and features. +

+ + +
``` @@ -63,7 +61,7 @@ Vue.component('anchored-heading', { }) ``` -That template doesn't feel great. It's not only verbose, but we're duplicating `` for every heading level and will have to do the same when we add the anchor element. The whole thing is also wrapped in a useless `div` because components must contain exactly one root node. +That template doesn't feel great. It's not only verbose, but we're duplicating `` for every heading level and will have to do the same when we add the anchor element. While templates work great for most components, it's clear that this isn't one of them. So let's try rewriting it with a `render` function: From 1b23c9294c3e1cb9eef929aa1fecdbf8d44718b7 Mon Sep 17 00:00:00 2001 From: Chris Fritz Date: Thu, 6 Jul 2017 02:41:52 -0400 Subject: [PATCH 0080/1339] initial prototype of team page locations --- src/v2/guide/team.md | 233 ++++++++++++++++++++++++- themes/vue/source/css/_animations.styl | 12 ++ themes/vue/source/css/_settings.styl | 1 + themes/vue/source/css/_team.styl | 35 ++++ themes/vue/source/css/page.styl | 68 ++++---- 5 files changed, 314 insertions(+), 35 deletions(-) create mode 100644 themes/vue/source/css/_animations.styl diff --git a/src/v2/guide/team.md b/src/v2/guide/team.md index 9d33a0c05c..7806253460 100644 --- a/src/v2/guide/team.md +++ b/src/v2/guide/team.md @@ -41,12 +41,32 @@ order: 31 + +
+ + Distance +
+
+ About {{ textDistance }} away in {{ profile.city }} +
+ +