Update Polymer version to 1.2.0

jamesliu96 · Oct 23, 2015 · 4ca6d85 · 4ca6d85
1 parent 5219f81
commit 4ca6d85
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 16 deletions.
diff --git a/1.0/articles/es6.md b/1.0/articles/es6.md
@@ -68,7 +68,7 @@ Extending `HTMLElement` creates the element with the correct `prototype`, inheri
 leaving it off the other examples on this page.
 {: .alert .alert-info }
 
-### Element "constructors" 
+### Element "constructors"
 
 Normally when creating a class, you define a `constructor` to do initialization work. However,
 in the world of custom elements this doesn't apply. Instead, you'll need to use
@@ -107,14 +107,14 @@ elements are created by the browser.
 
 One nice thing I'm doing here is using a [template string](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) to create Shadow DOM from an HTML snippet. Rather than concatenating strings or using escape sequences, we get a nicely formatted multiline string.
 
-### Adding properties and methods 
+### Adding properties and methods
 
 Say we wanted to add a `symbols` property to our element. Users should be able to
 configure the list of ticker symbols through the property:
 
     document.querySelector('stock-ticker').symbols = ["GOOG", "GOOGL"];
 
-and also declaratively, using an HTML attribute: 
+and also declaratively, using an HTML attribute:
 
     <stock-ticker symbols='["GOOG", "GOOGL"]'>Loading...</stock-ticker>
 
@@ -155,7 +155,7 @@ Check. It. Out! We're using ES6 [object shorthand](https://developer.mozilla.org
 
 ### Registering an element
 
-So far, we've only defined a custom element using class syntax. The last step is to register the tag. This tells the browser about the element and allows you to create instances. 
+So far, we've only defined a custom element using class syntax. The last step is to register the tag. This tells the browser about the element and allows you to create instances.
 
     class StockTicker extends HTMLElement {
       ...

diff --git a/1.0/docs/start/getting-the-code.md b/1.0/docs/start/getting-the-code.md
@@ -53,7 +53,7 @@ This generates a basic `bower.json` file. Some of the questions, like
 
 The next step is to install {{site.project_title}}:
 
-    bower install --save Polymer/polymer#^1.1.0
+    bower install --save Polymer/polymer#^1.2.0
 
 Bower adds a `bower_components/` folder in the root of your project and
 fills it with {{site.project_title}} and its dependencies.
@@ -64,7 +64,7 @@ fills it with {{site.project_title}} and its dependencies.
   "name": "my-project",
   "version": "0.0.0",
   "dependencies": {
-    "polymer": "Polymer/polymer#^1.1.0"
+    "polymer": "Polymer/polymer#^1.2.0"
   }
 }
 ```
@@ -83,7 +83,7 @@ This updates all packages in `bower_components/` to the latest stable version.
 
 Click the button to download {{site.project_title}} {% polymer_version_dir %} as a ZIP file.
 
-<p><a href="http://zipper.bowerarchiver.appspot.com/archive?polymer=Polymer/polymer%23%5E1.1.0">
+<p><a href="http://zipper.bowerarchiver.appspot.com/archive?polymer=Polymer/polymer%23%5E1.2.0">
   <paper-button class="cta" raised><core-icon icon="file-download"></core-icon>Download ZIP</paper-button>
 </a></p>
 
@@ -97,38 +97,38 @@ Expand the ZIP file in your project directory to create a `bower_components` fol
 
 Unlike Bower, the ZIP file doesn't provide a built-in method
 for updating dependencies. You can manually update components with a new ZIP
-file. 
+file.
 
-**Note:**  If you decide to install Bower later, you can use Bower to update the 
-components you installed from the ZIP file. Follow the instructions in 
+**Note:**  If you decide to install Bower later, you can use Bower to update the
+components you installed from the ZIP file. Follow the instructions in
 [Updating packages](#updatebower).
 {: .alert .alert-info }
 
 ## Using the Polyfills
 
 When you install {{site.project_title}} (either with Bower or as a ZIP), you get the
-[Web Components polyfill library](/0.5/docs/start/platform.html). 
-For this version of {{site.project_title}}, you need the `webcomponents-lite` version of the 
+[Web Components polyfill library](/0.5/docs/start/platform.html).
+For this version of {{site.project_title}}, you need the `webcomponents-lite` version of the
 library, which doesn't include the shadow DOM polyfill.
 
 Using the polyfills ensures that you can use {{site.project_title}} with browsers that don't support
 the Web Components specifications natively.
 
 ## Element starter {#seed-element}
 
-If you want to publish an element for others to use, [the 
+If you want to publish an element for others to use, [the
 `<seed-element>` boilerplate](https://github.com/polymerelements/seed-element) is a good starting point. It comes with the tools
 you need for building, testing and documenting your element.
 
-[Create a reusable element](reusableelements.html) guides you through the 
+[Create a reusable element](reusableelements.html) guides you through the
 steps to create, test, document and publish your element.
 
 ## Polymer Starter Kit {#psk}
 
-A “batteries-included” application template, the 
+A “batteries-included” application template, the
 [Polymer Starter Kit](https://developers.google.com/web/tools/polymer-starter-kit/)
 includes a responsive application layout, tooling for testing and deployment, and
-even optional support for advanced features like offline access and push notifications. 
+even optional support for advanced features like offline access and push notifications.
 
 ## Contributing to the Project {#using-git}