docs(cookbook/graphql): Fix jade paths after rebase

Author: Urigo

public/docs/_examples/toh-4/ts/src/app/hero.ts

@@ -1,3 +1,4 @@
+// #docregion
 export class Hero {
   id: number;
   name: string;

public/docs/ts/latest/cookbook/graphql.jade

@@ -96,9 +96,9 @@ include ../_util-fns
   the data might change and not be consistent across the app
 
   #### Using a service
-  
-+makeExample('toh-6/ts/app/hero.service.ts', 'getHero','hero.service.ts (Fetch by Id)')
-+makeExample('toh-6/ts/app/hero-detail.component.ts', 'service-fetch-by-id','hero-detail.component.ts (Fetch by Id)')
+
++makeExample('toh-6/ts/src/app/hero.service.ts', 'getHero','hero.service.ts (Fetch by Id)')
++makeExample('toh-6/ts/src/app/hero-detail.component.ts', 'service-fetch-by-id','hero-detail.component.ts (Fetch by Id)')
 :marked
   The problems with that approach:
 
@@ -109,9 +109,9 @@ include ../_util-fns
 
   #### Fetch data at the parent component and pass it down the component tree
 
-+makeExample('toh-4/ts/app/hero.ts','','Declare the API type')
-+makeExample('toh-4/ts/app/hero-detail.component.ts','declaring-conponent-input','Declare the input')
-+makeExample('toh-4/ts/app/app.component.ts','calling-component','Using from parent')
++makeExample('toh-4/ts/src/app/hero.ts','','Declare the API type')
++makeExample('toh-4/ts/src/app/hero-detail.component.ts','declaring-conponent-input','Declare the input')
++makeExample('toh-4/ts/src/app/app.component.ts','calling-component','Using from parent')
 :marked
   The problems with that approach:
 
@@ -121,16 +121,16 @@ include ../_util-fns
 
   #### Solution - Component based API
 
-+makeExample('heroes-graphql/ts/app/hero-detail.component.ts','graphql-query','GraphQL query')
++makeExample('heroes-graphql/ts/src/app/hero-detail.component.ts','graphql-query','GraphQL query')
 :marked
   As you can see, we placed the data dependency inside or next to the component itself and when the data dependency changes,
   the component is the only thing that needed to be changed -
   no service or parent component were harmed in the making of this component.
 
   So now when we want to change the data dependencies, all changes are contained within the single component:
 
-+makeExample('heroes-graphql/ts/app/hero-detail.component.1.ts','graphql-query-new-field','Adding `age` field to component')
-+makeExample('heroes-graphql/ts/app/hero-detail.component.1.html','template-new-field','Adding `age` field to template')  
++makeExample('heroes-graphql/ts/src/app/hero-detail.component.1.ts','graphql-query-new-field','Adding `age` field to component')
++makeExample('heroes-graphql/ts/src/app/hero-detail.component.1.html','template-new-field','Adding `age` field to template')  
 :marked
   ### Network Performance
 
@@ -183,13 +183,13 @@ code-example(language="sh" class="code-shell").
   Now let's initialize our client.
 
   Create a new file called `client.ts` and place the following code:
-+makeExample('heroes-graphql/ts/app/client.1.ts')
++makeExample('heroes-graphql/ts/src/app/client.1.ts')
 :marked
   This is the default initialization of Apollo and will call the `/graphql` endpoint.
 
   In order to change the [settings](http://dev.apollodata.com/core/apollo-client-api.html#ApolloClient\.constructor) of Apollo client,
   we will call it's constructor with different parameters, for example in order to change the endpoint we will do something like that:
-+makeExample('heroes-graphql/ts/app/client.2.ts', 'network-initialization')
++makeExample('heroes-graphql/ts/src/app/client.2.ts', 'network-initialization')
 .l-sub-section
   :marked
     If you don't have a GraphQL server running, [jump to the section about creating a GraphQL server](#server).
@@ -198,8 +198,8 @@ code-example(language="sh" class="code-shell").
 
 :marked
   Once we've finished initializing our Apollo-Client, we would want to add the Apollo module to our app's NgNodules with our configurations:
-+makeExample('heroes-graphql/ts/app/app.module.ts', 'import-apollo', 'app.module.ts (npm imports)')
-+makeExample('heroes-graphql/ts/app/app.module.ts', 'apollo-ngmodule', 'app.module.ts (NgModule)')
++makeExample('heroes-graphql/ts/src/app/app.module.ts', 'import-apollo', 'app.module.ts (npm imports)')
++makeExample('heroes-graphql/ts/src/app/app.module.ts', 'apollo-ngmodule', 'app.module.ts (NgModule)')
 
 .l-main-section
 <a id="querying"></a>
@@ -208,22 +208,22 @@ code-example(language="sh" class="code-shell").
 
   In GraphQL we always query a server which has a schema representing the data it exposes.
   Our server is built based on the Heroes tutorial and here is the schema:
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'graphql-schema', 'Heroes GraphQL Schema')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'graphql-schema', 'Heroes GraphQL Schema')
 :marked
   So let's start by adding Apollo into our Component, let's import it and inject with in the constructor:
-+makeExample('heroes-graphql/ts/app/heroes.component.ts', 'import-apollo', 'heroes.component.ts')
-+makeExample('heroes-graphql/ts/app/heroes.component.ts', 'inject-apollo', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.ts', 'import-apollo', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.ts', 'inject-apollo', 'heroes.component.ts')
 :marked
   To query data with Apollo Client we just need to pass Apollo a query in the GraphQL query syntax, explained [here](http://graphql.org/learn/queries/).
 
   In order to parse regular string literals as GraphQL, we will use the `gql` function from the `graphql-tag` library:
-+makeExample('heroes-graphql/ts/app/heroes.component.ts', 'import-graphql-tag', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.ts', 'import-graphql-tag', 'heroes.component.ts')
 :marked
   Now let's query:
-+makeExample('heroes-graphql/ts/app/heroes.component.ts', 'query-heroes', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.ts', 'query-heroes', 'heroes.component.ts')
 :marked
   and render:
-+makeExample('heroes-graphql/ts/app/heroes.component.1.html', 'render-heroes', 'heroes.component.html')
++makeExample('heroes-graphql/ts/src/app/heroes.component.1.html', 'render-heroes', 'heroes.component.html')
 
 
 .l-main-section
@@ -267,13 +267,13 @@ code-example(language="json").
     You can get deep into the mutation syntax on the [GraphQL.org website](http://graphql.org/learn/queries/#mutations)
 :marked
   So first let's add a local function to add a hero to our template:
-+makeExample('heroes-graphql/ts/app/heroes.component.html', 'add', 'heroes.component.html')  
++makeExample('heroes-graphql/ts/src/app/heroes.component.html', 'add', 'heroes.component.html')  
 :marked
   and component:
-+makeExample('heroes-graphql/ts/app/heroes.component.1.ts', 'add', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.1.ts', 'add', 'heroes.component.ts')
 :marked
   and now let's add an `addHero` mutation to that function using the `apollo.mutate` function:
-+makeExample('heroes-graphql/ts/app/heroes.component.ts', 'add-mutation', 'heroes.component.ts')
++makeExample('heroes-graphql/ts/src/app/heroes.component.ts', 'add-mutation', 'heroes.component.ts')
 :marked
   You can see, that our mutation requires and variable and we pass it to the `mutate` function through the `variables` param.
 
@@ -327,13 +327,13 @@ code-example(language="sh" class="code-shell").
     npm install graphql-tools --save  
 :marked
   Now for the schema itself:    
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'graphql-schema', 'Heroes GraphQL Schema')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'graphql-schema', 'Heroes GraphQL Schema')
 .l-sub-section
   :marked
     The schema is pretty self explanatory, but if you want to dig deeper, check out [GraphQL.org `learn` section](http://graphql.org/learn/)
 :marked
   Next let's create our in-memory data:  
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'heroes-array', 'Heroes Array')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'heroes-array', 'Heroes Array')
 :marked
   Now we need to write a server that will resolve the queries that we will get from the client based on the schema.
 
@@ -343,10 +343,10 @@ code-example(language="sh" class="code-shell").
     For the full explanation about how GraphQL resolvers work check out the [execution section](http://graphql.org/learn/execution/) of GraphQL.org 
 :marked
   Let's create our resolvers:
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'resolvers', 'Resolvers')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'resolvers', 'Resolvers')
 :marked
   We also used some functions from `lodash` so don't forget to install them from npm and import them:
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'import-lodash', 'Importing lodash')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'import-lodash', 'Importing lodash')
 :marked
   As you can see, we created functions that correspond to each type of our schema and also to the mutations.
 
@@ -359,15 +359,15 @@ code-example(language="sh" class="code-shell").
 :marked
   Now we need to connect the shema to the resolvers with the `makeExecutableSchema` function from 
   the [graphql-tools](http://dev.apollodata.com/tools/graphql-tools/index.html) library:
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'import-graphql-tools', 'importing graphql-tools')
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'make-executable-schema', 'makeExecutableSchema')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'import-graphql-tools', 'importing graphql-tools')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'make-executable-schema', 'makeExecutableSchema')
 :marked
   Now that we have executable schema, let's execute it using the `graphql` library and export it so we can use it in our Apollo Client:
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'import-graphql', 'Dont forget to npm install')
-+makeExample('heroes-graphql/ts/app/in-memory-graphql.ts', 'execute-and-export', 'Execute and export')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'import-graphql', 'Dont forget to npm install')
++makeExample('heroes-graphql/ts/src/app/in-memory-graphql.ts', 'execute-and-export', 'Execute and export')
 :marked
   Now all that's left is to connect the new in-memory server into our Apollo Client configuration:
-+makeExample('heroes-graphql/ts/app/client.ts', '', 'client.ts')
++makeExample('heroes-graphql/ts/src/app/client.ts', '', 'client.ts')
 :marked
   That's it.  now you can run your application as if you had a GraphQL server connected to it but, 
   there is no persistance - everything is running in-memory browser right now, so when you refresh the page, all changes will be lost.
@@ -385,15 +385,15 @@ code-example(language="sh" class="code-shell").
 
 block file-summary
   +makeTabs(
-    `heroes-graphql/ts/app/app.component.ts,
-     heroes-graphql/ts/app/app.module.ts,
-     heroes-graphql/ts/app/heroes.component.ts,
-     heroes-graphql/ts/app/heroes.component.html,
-     heroes-graphql/ts/app/heroes.component.css,
-     heroes-graphql/ts/app/hero-detail.component.ts,
-     heroes-graphql/ts/app/hero-detail.component.html,
-     heroes-graphql/ts/app/in-memory-graphql.ts,
-     heroes-graphql/ts/app/client.ts`,
+    `heroes-graphql/ts/src/app/app.component.ts,
+     heroes-graphql/ts/src/app/app.module.ts,
+     heroes-graphql/ts/src/app/heroes.component.ts,
+     heroes-graphql/ts/src/app/heroes.component.html,
+     heroes-graphql/ts/src/app/heroes.component.css,
+     heroes-graphql/ts/src/app/hero-detail.component.ts,
+     heroes-graphql/ts/src/app/hero-detail.component.html,
+     heroes-graphql/ts/src/app/in-memory-graphql.ts,
+     heroes-graphql/ts/src/app/client.ts`,
     ',,,,,,,,',
     `app.comp...ts,
      app.mod...ts,
@@ -407,10 +407,10 @@ block file-summary
   )
 
   +makeTabs(
-   `heroes-graphql/ts/app/app-routing.module.ts,
-    heroes-graphql/ts/app/hero-search.component.ts,
-    heroes-graphql/ts/app/hero-search.component.html,
-    heroes-graphql/ts/app/hero-search.component.css`,
+   `heroes-graphql/ts/src/app/app-routing.module.ts,
+    heroes-graphql/ts/src/app/hero-search.component.ts,
+    heroes-graphql/ts/src/app/hero-search.component.html,
+    heroes-graphql/ts/src/app/hero-search.component.css`,
     null,
    `app-routing.modules.ts,
     hero-search.component.ts,