Fix formatting that broke due to github changes

Author: steveschmitt

_config.yml

@@ -1,9 +1,10 @@
 markdown: kramdown
-highlighter: rouge
 
 kramdown:
    input: GFM
    hard_wrap: false
+   syntax_highlighter: rouge
+   syntax_highlighter_opts: { default_lang: javascript }
 
 url: http://breeze.github.io
 

_includes/metadata-schema.md

@@ -1,4 +1,4 @@
-#Metadata schema#
+# Metadata schema #
 
 The following is the schema for breeze metadata described as a json.schema document ( see [http://json-schema.org](http://json-schema.org)  ).
 

doc-breeze-labs/ajax-post.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/breezeajaxpostjs.html"
 ---
-#Breeze queries using POST#
+# Breeze queries using POST #
 This feature is for handling large object graphs as query parameters - object graphs so large that they won't fit in a URL.
 It updates the [Breeze AJAX adapter](/doc-js/server-ajaxadapter) to allow HTTP POST 
 for specially-constructed [.withParameters](/doc-js/api-docs/classes/EntityQuery.html#method_withParameters)
@@ -12,7 +12,7 @@ It works by telling jQuery's AJAX implementation, or Angular's $http service, to
 
 This is an add-on to Breeze, and POST requires changes to the way your `.withParameters` queries are structured, so don't use it unless you really need it.
 
-##Installation
+## Installation
 Get [breeze.ajaxpost.js](https://github.com/Breeze/breeze.js.labs/blob/master/breeze.ajaxpost.js) from GitHub.
 
 In your HTML file (e.g. index.html), add a script tag for **breeze.ajaxpost.js** ***after*** the breeze library:
@@ -34,7 +34,7 @@ That's fine if you're using breeze's *default* ajax adapter. If you change the a
         //... your service logic
     }]);
 
-##Usage
+## Usage
 Server side method using GET (example using .NET Web API):
 
         [HttpGet]
@@ -76,8 +76,8 @@ Special parameters:
 - $encoding: ‘JSON’ or x-www-form-urlencoded (the default)
 - $data: contains the data to be sent to the server
 
-##Examples
-###Live POST queries
+## Examples
+### Live POST queries
 
 A StackOverflow question prompted us to produce [**this plunker example**](http://plnkr.co/edit/nhXIG62BDJpEJE77oLFT?p=info) of an Angular app making POST queries to a cross-origin server. All app JavaScript is in the *script.js* file. Be sure to follow along with the *README.md* which describes the mechanics in detail.
 

doc-breeze-labs/directives-float.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/breezedirectivesfloat.html"
 ---
-#Angular Float Directive
+# Angular Float Directive
 
 The `zFloat` directive tells Angular to display the view value rather than the floating point
 model value when the view and model values are "equivalent".

doc-breeze-labs/directives-validation.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/directivesvalidation.html"
 ---
-#Breeze Labs: AngularJS Validation and Required Indicator Directive
+# Breeze Labs: AngularJS Validation and Required Indicator Directive
 
 The **`zValidate`** Breeze/AngularJS validation directive displays and entity property's validation errors on screen. It can also visually identifies a required property with an asterisk.
 
@@ -21,7 +21,7 @@ And if there is an error, it displays like this:
 
 <img alt="zValidate error message" src="/images/samples/z-validate-firstNameRequiredError.png" style="width: 100%; max-width: 726px;" />
 
-##Breeze validation
+## Breeze validation
 
 Breeze entities have built-in model-level validation driven by metadata that describe client-side validation rules for properties and entities. Breeze invokes these rules automatically during four phases of the entity life-cycle (attached, queried, property changed, saved).  You also can invoke these rules programmatically at any time. 
 
@@ -33,15 +33,15 @@ Those sources describe how to define validation rules and how to invoke them. Th
 
 But we can show you *one way* to present errors that you may use for inspiration or "as is". That's the purpose of this Breeze Lab.
 
-##Display errors with the zValidate directive
+## Display errors with the zValidate directive
 
 The `zValidate` directive is a way to display property validation errors as error messages adjacent to the errant data value.
 
 A <a href="http://docs.angularjs.org/guide/directive" target="_blank"><em>directive</em></a> is the AngularJS mechanism for manipulating the browser DOM programmatically as part of the Angular binding process. 
 
 Angular ships with a core set of directives that cover many scenarios. But they can't cover everything and you are encouraged to extend the Angular binding system with your own directives as we are doing in this lab project.
 
-##Sample
+## Sample
 
 Perhaps the best way to understand this directive is to see it in a live example of a "Person Edit" screen.
 
@@ -63,15 +63,15 @@ While this sample demonstrates the `zValidate` directive, it coincidentally demo
 
 Let's tour the sample code.
 
-###Load the directive files
+### Load the directive files
 
 Pick "index.html" from the "Source Code" drop down (you can get back to the displayed result by clicking the "forward" triangle button in the upper right).  Scroll to the scripts near the bottom.
 
 The `zValidate` directive is defined in <a href="https://github.com/Breeze/breeze.js.labs/blob/master/breeze.directives.js" target="_blank">breeze.directives.js</a>. Notice that we load this script ***after*** loading the angular and breeze JavaScript files and ***before*** loading any application JavaScript files.
 
 The directive paints error error messages and the required indicator with default templates that depend upon CSS classes defined in <a href="https://github.com/Breeze/breeze.js.labs/blob/master/breeze.directives.css" target="_blank">breeze.directives.css</a>. Scroll to the top where we loaded that CSS file among the other CSS files. Alternatively, we could have incorporated its contents within the application "style.css".
 
-###Apply the directive
+### Apply the directive
 The application is ready to display property validation errors. 
 
 You decide which data bound HTML controls should have this behavior by applying the `zValidate` directive as an attribute of that control. In this sample, we apply it to every textbox. Here is the markup for the "First Name" textbox:
@@ -99,7 +99,7 @@ Returning to the binding expression, we see that ViewModel (`vm`) exposes a `per
 
 The directive drew a red asterisk next to the textbox to indicate that the first name is required. We'll see how it knew to do that in a little bit.
 
-###Validators
+### Validators
 You can create and remove validation errors by playing with the textbox values. Breeze monitors your changes and updates the validation error(s) for each property accordingly. Angular updates the property with every keystroke so you get an immediate visual response.
 
 Where are the validators defined? Open the "model.js" via the "Source code" combobox. Look at the `configureMetadataStore` method.
@@ -115,11 +115,11 @@ The `configureMetadataStore` method has three steps.
 2. Add the `Person` entity type to the metadata
 3. Discover and register all properties with a "required" validation.
 
-###Create a custom validator
+### Create a custom validator
 
 Most of the Person properties are validated with stock validators, shipped with Breeze. A "twitter" validator is not one of them so we had to write one. Check it out; notice that it's built with the Breeze RegularExpression validator factory method.
 
-###Client-side metadata
+### Client-side metadata
 This sample doesn't get data from a server. We're either editing a faked `Person` or a newly created `Person` entity that we won't save. There is no server. There is no server-supplied metadata.
 
 A Breeze client needs metadata. Fortunately, we can define that metadata in JavaScript on the client ... which we do in the `addPersonType` method.
@@ -135,7 +135,7 @@ firstName:  { dataType: DT.String,
 
 The `firstName` definition includes two stock validators: `required` and `maxLength`. The stock validators are produced by generator functions that are static members of the Breeze `Validator` class. We trust you can follow the pattern for the remaining properties.
 
-###Required property indicator
+### Required property indicator
 
 The directive can paint a ***required property indicator*** next to the input control or combobox bound to a required property.
 
@@ -156,7 +156,7 @@ If you add custom validators that should be treated as required, add `.isRequire
             }
         }
 
-###Reconfiguring the error and required templates
+### Reconfiguring the error and required templates
 
 The `zValidate` directive has a default template for displaying errors and another template for displaying the required indicator. 
 
@@ -173,7 +173,7 @@ The app is resetting the templates (see the`configDirective` method)  during the
 
 >See the Angular <a href="http://docs.angularjs.org/guide/module" target="_blank">documentation for modules</a> to learn about the life-cycle of an Angular module and "configuration blocks" in particular.
 
-##zValidate in a repeater 
+## zValidate in a repeater 
 This sample shows how you can display validation messages while editing a single `Person` entity. What if the screen presented many `Person` entities and you wanted to see all of their property validation error messages?
 
 You can do that in the manner you'd expect.
@@ -185,7 +185,7 @@ You can do that in the manner you'd expect.
 &lt;/li>
 </pre> 
 
-##Why not use HTML5 or Angular validation
+## Why not use HTML5 or Angular validation
 
 HTML 5 defines a collection of <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Forms/Data_form_validation" target="_blank">form validation attributes</a>. Angular forms and controls have <a href="http://docs.angularjs.org/guide/forms" target="_blank">built-in validation services</a>. Why not use either of these facilities instead of Breeze validation?
 
@@ -209,23 +209,23 @@ Fortunately, there is a practical argument to bolster the philosophical: **the `
 
 Markup validation makes sense when you are binding to a simple object that doesn't have its own business rules. It is a convenient declarative alternative to writing a lot of validation JavaScript in the ViewModel. But Breeze entities come equipped, out-of-the-box with a metadata-driven, extensible, model validation mechanism which is both more powerful and easier to use. Skip the markup validation and go straight to the source ... with `zValidate`.
 
-##Limitations
+## Limitations
 The approach described and implemented in this directive doesn't cover every scenario.
 
-###Property errors only
+### Property errors only
 
 This directive displays property validation errors only. The entity may have errors that are not specific to a particular entity. You'll need to find another way to display them.
 
-###Message location and format
+### Message location and format
 You can configure the "required" and "error" templates but the directive is written to display those templates in a particular location relative to the data bound HTML control. You'll have to revise the directive if that doesn't suit your needs.
 
-###Only input controls
+### Only input controls
 The directive only works for HTML controls with the `ngModel` directive which is to say, with controls that accept user input. If you wanted to display error messages next to a read-only display of person properties, you would probably revise the directive to get the property info from `ngBind` and devise another way to present the error message. 
 
-###Multiple errors
+### Multiple errors
 A property can have multiple validation errors. This directive concatenates their error messages, separated by semi-colons (;). You'll have to revise the directive if you want different behavior.
 
-##What about Knockout?
+## What about Knockout?
 This directive is an Angular solution.
 
 We love Knockout too. We expect to write a <a href="http://knockoutjs.com/documentation/custom-bindings.html" target="_blank">Knockout Custom Binding</a> that implements the same behavior with the same simplicity of application.

doc-breeze-labs/get-entity-graph.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/getentitygraph.html"
 ---
-#Get entity graph from cache
+# Get entity graph from cache
 
 Sometimes you hold one more root entities and want both those roots **and their related entities** in a single array. That array represents the "entityGraph" of the root(s).
 

doc-breeze-labs/index.md

@@ -10,17 +10,17 @@ These projects leverage the in-depth knowledge of BreezeJS team members and cust
 
 Breeze Labs projects are all open-source. If a project doesn't yet fully meet your specific needs, you are invited to get involved, help out, fork and clone and submit pull requests. 
 
-##Getting Started
+## Getting Started
 
 Each Breeze Labs project is designed to provide drop-in capabilities for your apps, support for your development workflow or example implementations of common Breeze app patterns. Most projects reside on GitHub within the <a href="https://github.com/Breeze/breeze.js.labs" target="_blank">breeze.js.labs repository</a> although some may live in separate repositories. 
 
 Every project has its own guide, either within this documentation, in the project, or both.
 
-##License
+## License
 
 Breeze Labs projects are all released under the <a href="http://opensource.org/licenses/mit-license.php" target="_blank">MIT license</a>. This license applies ONLY to the labs project-specific source and does not extend to Breeze itself, or any other 3rd party libraries used in a repository. For licensing information about BreezeJS, see the [License Agreement page](/doc-main/license).
 
-##Support
+## Support
 
 While the Breeze Labs projects are stewarded in part by members of the BreezeJS team, these projects are not covered under the support agreements afforded to Breeze commercial and trial license holders. Breeze Labs projects do not provide official Breeze features and are not to be considered part of any version of Breeze. As such, these projects are not officially supported by the BreezeJS team. Any and all support requests should be directed to <a href="http://stackoverflow.com/questions/tagged/breeze?sort=newest" target="_blank">StackOverflow and tagged with "breeze"</a>.
 

doc-breeze-labs/metadata-helper.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/breezemetadata-helperjs.html"
 ---
-#Breeze MetadataHelper#
+# Breeze MetadataHelper #
 The Breeze Labs **MetadataHelper** script extends Breeze with a `MetadataHelper` class. Visit the "[Metadata By Hand](/doc-js/metadata-by-hand#addTypeToStore)" topic to learn how `MetadataHelper` methods can reduce error prone repetition in your configuration and improve the metadata authoring experience.
 
 You can download breeze.metadata-helper.js 

doc-breeze-labs/save-error-extensions.md

@@ -2,7 +2,7 @@
 layout: doc-breeze-labs
 redirect_from: "/old/documentation/saveerrorextensionsjs.html"
 ---
-#saveErrorExtensions.js
+# saveErrorExtensions.js
 
 A Breeze Labs plugin that extends Breeze with a method that creates useful error messages from the error data passed to the failure callback when `EntityManager.saveChanges` fails.
 

doc-cool-breezes/knockout-circular-refs.md

@@ -2,7 +2,7 @@
 layout: doc-cool-breezes
 redirect_from: "/old/documentation/knockout-circular-references.html"
 ---
-#Grids and Knockout circular references#
+# Grids and Knockout circular references #
 
 We may run into trouble when we try to display Breeze entities in a vendor grid control.
 
@@ -50,7 +50,7 @@ After <span class="codeword">ko.toJS</span> unwraps the entities, we iterate ove
 
 If the entities had navigation properties that were giving you trouble, you could follow the pattern and zap them too.</p>
 
-##Consider projections instead##
+## Consider projections instead ##
 You may be paying a double performance price when you don't have to. The query may be pulling more data over the wire than you need to display. And <span class="codeword">ko.toJS</span> may be copying values that you aren't going to display either.
 
 The cost may be negligible and having those entities in cache for some future purpose could save you unnecessary server trips down the line. Only you know what's best for your application.