create-sitecore-jss 22.2.0-canary.9 → 22.2.0

package/dist/templates/angular/server.bundle.ts

@@ -6,9 +6,6 @@ import 'zone.js';
 import { JssRouteBuilderService } from './src/app/routing/jss-route-builder.service';
 import { environment } from './src/environments/environment';
 import { AppServerModule, renderModule } from './src/main.server';
-import { clientFactory } from './src/app/lib/graphql-client-factory';
-import { dictionaryServiceFactory } from './src/app/lib/dictionary-service-factory';
-import { layoutServiceFactory } from './src/app/lib/layout-service-factory';
 
 export * from './src/main.server';
 
@@ -102,20 +99,5 @@ function parseRouteUrl(url: string) {
 
 const apiKey = environment.sitecoreApiKey;
 const siteName = environment.sitecoreSiteName;
-const defaultLanguage = environment.defaultLanguage;
-const graphQLEndpointPath = environment.graphQLEndpointPath;
-const graphQLEndpoint = environment.graphQLEndpoint;
 
-export {
-  renderView,
-  parseRouteUrl,
-  setUpDefaultAgents,
-  apiKey,
-  siteName,
-  clientFactory,
-  dictionaryServiceFactory,
-  layoutServiceFactory,
-  defaultLanguage,
-  graphQLEndpointPath,
-  graphQLEndpoint,
-};
+export { renderView, parseRouteUrl, setUpDefaultAgents, apiKey, siteName };

package/dist/templates/{angular-sxp → angular}/sitecore/config/{{appName}}.config

@@ -1,90 +1,90 @@
-<!--
-  JSS Sitecore Configuration Patch File
-
-  This configuration file registers the JSS site with Sitecore, and configures the Layout Service
-  to work with it. Config patches need to be deployed to the Sitecore server.
-
-  Normally `jss deploy config` can do this for local development. To manually deploy, or to deploy via CI,
-  this file can be placed in the `App_Config/Include` folder, or a subfolder of it, within the Sitecore site.
--->
-<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"
-               xmlns:set="http://www.sitecore.net/xmlconfig/set/"
-               xmlns:role="http://www.sitecore.net/xmlconfig/role/">
-  <sitecore>
-    <settings>
-      <!--
-        PROXY CONFIGURATION
-        When running JSS with the headless proxy (node-headless-ssr-proxy),
-        the original IP address of clients is obscured by the proxy.
-        This setting tells Sitecore to read the forwarded header the proxy sends,
-        thus making analytics track the correct original client IP address.
-      -->
-      <setting name="Analytics.ForwardedRequestHttpHeader" set:value="X-Forwarded-For" />
-    </settings>
-    <sites>
-      <!--
-        JSS Site Registration
-        This configures the site with Sitecore - i.e. host headers, item paths.
-        If your JSS app lives within an existing Sitecore site, this may not be necessary.
-
-        IMPORTANT: JSS sites ship in 'live mode', which makes development and testing easy,
-        but disables workflow and publishing. Before going to production, change the `database`
-        below to `web` instead of `master`.
-      -->
-      <site patch:before="site[@name='website']"
-            inherits="website"
-            name="<%- appName %>"
-            hostName="<%- hostName.replace(/^https?:\/\//, '') %>"
-            rootPath="/sitecore/content/<%- appName %>"
-            startItem="/home"
-            database="master" />
-    </sites>
-    <javaScriptServices>
-      <apps>
-        <!--
-          JSS App Registration
-          The JSS app needs to be registered in order to support layout service and import services.
-
-          There are many available attributes, and they inherit the defaults if not explicitly specified here.
-          Defaults are defined in `/App_Config/Sitecore/JavaScriptServices/Sitecore.JavaScriptServices.Apps.config`
-
-          NOTE: graphQLEndpoint enables _Integrated GraphQL_. If not using integrated GraphQL, it can be removed.
-
-          NOTE: layoutServiceConfiguration should be set to "default" when using GraphQL Edge schema.
-          When using integrated GraphQL with Edge schema, a $language value is injected
-          since language is required in all Edge queries. "jss" configuration does not do this (which is backwards
-          compatible with JSS versions < 18.0.0).
-        -->
-        <app name="<%- appName %>"
-             layoutServiceConfiguration="default"
-             sitecorePath="/sitecore/content/<%- appName %>"
-             inherits="defaults"
-             useLanguageSpecificLayout="true"
-             graphQLEndpoint="/sitecore/api/graph/edge" />
-      </apps>
-      <!--
-        IMAGE RESIZING WHITELIST
-        Using Sitecore server-side media resizing (i.e. the `imageParams` or `srcSet` props on the `<Image/>` helper component)
-        could expose your Sitecore server to a denial-of-service attack by rescaling an image with many arbitrary dimensions.
-        In JSS resizing param sets that are unknown are rejected by a whitelist.
-
-        Sets of image sizing parameters that are used in app components must be whitelisted here.
-        If a param set is not whitelisted, the image will be returned _without resizing_.
-
-        To determine the image parameters being used, look at the query string on the `src` of the rendered image, i.e. '/img.jpg?mw=100&h=72' -> mw=100,h=72
-        Note: the parameter sets defined here are comma-delimited (,) instead of &-delimited like the query string. Multiple sets are endline-delimited.
-      -->
-      <allowedMediaParams>
-        <!-- XML element name is arbitary, useful for organizing and patching -->
-        <styleguide-image-sample>
-          mw=100,
-          mh=50
-        </styleguide-image-sample>
-        <styleguide-image-sample-adaptive>
-          mw=300
-          mw=100
-        </styleguide-image-sample-adaptive>
-      </allowedMediaParams>
-    </javaScriptServices>
-  </sitecore>
-</configuration>
+<!--
+  JSS Sitecore Configuration Patch File
+
+  This configuration file registers the JSS site with Sitecore, and configures the Layout Service
+  to work with it. Config patches need to be deployed to the Sitecore server.
+
+  Normally `jss deploy config` can do this for local development. To manually deploy, or to deploy via CI,
+  this file can be placed in the `App_Config/Include` folder, or a subfolder of it, within the Sitecore site.
+-->
+<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"
+               xmlns:set="http://www.sitecore.net/xmlconfig/set/"
+               xmlns:role="http://www.sitecore.net/xmlconfig/role/">
+  <sitecore>
+    <settings>
+      <!--
+        PROXY CONFIGURATION
+        When running JSS with the headless proxy (node-headless-ssr-proxy),
+        the original IP address of clients is obscured by the proxy.
+        This setting tells Sitecore to read the forwarded header the proxy sends,
+        thus making analytics track the correct original client IP address.
+      -->
+      <setting name="Analytics.ForwardedRequestHttpHeader" set:value="X-Forwarded-For" />
+    </settings>
+    <sites>
+      <!--
+        JSS Site Registration
+        This configures the site with Sitecore - i.e. host headers, item paths.
+        If your JSS app lives within an existing Sitecore site, this may not be necessary.
+
+        IMPORTANT: JSS sites ship in 'live mode', which makes development and testing easy,
+        but disables workflow and publishing. Before going to production, change the `database`
+        below to `web` instead of `master`.
+      -->
+      <site patch:before="site[@name='website']"
+            inherits="website"
+            name="<%- appName %>"
+            hostName="<%- hostName.replace(/^https?:\/\//, '') %>"
+            rootPath="/sitecore/content/<%- appName %>"
+            startItem="/home"
+            database="master" />
+    </sites>
+    <javaScriptServices>
+      <apps>
+        <!--
+          JSS App Registration
+          The JSS app needs to be registered in order to support layout service and import services.
+
+          There are many available attributes, and they inherit the defaults if not explicitly specified here.
+          Defaults are defined in `/App_Config/Sitecore/JavaScriptServices/Sitecore.JavaScriptServices.Apps.config`
+
+          NOTE: graphQLEndpoint enables _Integrated GraphQL_. If not using integrated GraphQL, it can be removed.
+
+          NOTE: layoutServiceConfiguration should be set to "default" when using GraphQL Edge schema.
+          When using integrated GraphQL with Edge schema, a $language value is injected
+          since language is required in all Edge queries. "jss" configuration does not do this (which is backwards
+          compatible with JSS versions < 18.0.0).
+        -->
+        <app name="<%- appName %>"
+             layoutServiceConfiguration="default"
+             sitecorePath="/sitecore/content/<%- appName %>"
+             inherits="defaults"
+             useLanguageSpecificLayout="true"
+             graphQLEndpoint="/sitecore/api/graph/edge" />
+      </apps>
+      <!--
+        IMAGE RESIZING WHITELIST
+        Using Sitecore server-side media resizing (i.e. the `imageParams` or `srcSet` props on the `<Image/>` helper component)
+        could expose your Sitecore server to a denial-of-service attack by rescaling an image with many arbitrary dimensions.
+        In JSS resizing param sets that are unknown are rejected by a whitelist.
+
+        Sets of image sizing parameters that are used in app components must be whitelisted here.
+        If a param set is not whitelisted, the image will be returned _without resizing_.
+
+        To determine the image parameters being used, look at the query string on the `src` of the rendered image, i.e. '/img.jpg?mw=100&h=72' -> mw=100,h=72
+        Note: the parameter sets defined here are comma-delimited (,) instead of &-delimited like the query string. Multiple sets are endline-delimited.
+      -->
+      <allowedMediaParams>
+        <!-- XML element name is arbitary, useful for organizing and patching -->
+        <styleguide-image-sample>
+          mw=100,
+          mh=50
+        </styleguide-image-sample>
+        <styleguide-image-sample-adaptive>
+          mw=300
+          mw=100
+        </styleguide-image-sample-adaptive>
+      </allowedMediaParams>
+    </javaScriptServices>
+  </sitecore>
+</configuration>

package/dist/templates/{angular-sxp → angular}/sitecore/definitions/components/graph-ql-integrated-demo.sitecore.graphql

@@ -1,71 +1,71 @@
-# This file contains a GraphQL query that will be executed and the result provided to
-# your JSS component. You can run this query in GraphiQL ($endpoint/ui) for a nice editing experience.
-
-# Note that we're executing _two queries_ (datasource and contextItem)
-# within the context of the IntegratedDemoQuery _operation_. This makes it
-# very efficient at gathering data from multiple sources.
-
-query IntegratedDemoQuery($datasource: String!, $contextItem: String!, $language: String!) {
-  # Datasource query
-  # $datasource will always be set to the ID of the rendering's datasource item
-  # (as long as the GraphQLData helper is used)
-  datasource: item(path: $datasource, language: $language) {
-    id
-    name
-    # Strongly-typed querying on known templates is possible!
-    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>GraphQLIntegratedDemo {
-      # Single-line text field
-      sample1 {
-        # the 'jsonValue' field is a JSON blob that represents the object that
-        # should be passed to JSS field rendering helpers (i.e. text, image, link)
-        jsonValue
-        value
-      }
-      # General Link field
-      sample2 {
-        jsonValue
-        # Structured querying of the field's values is possible
-        text
-        target
-        url
-        # Access to the template definition is possible
-        definition {
-          type
-          shared
-        }
-      }
-    }
-  }
-
-  # Context/route item query
-  # $contextItem will always be set to the ID of the current context item (the route item)
-  # (as long as the GraphQLData helper is used)
-  contextItem: item(path: $contextItem, language: $language) {
-    id
-    # Get the page title from the app route template
-    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
-      pageTitle {
-        value
-      }
-    }
-
-    # List the children of the current route
-    children(hasLayout: true) {
-      results {
-        id
-        # typing fragments can be used anywhere!
-        # so in this case, we're grabbing the 'pageTitle'
-        # field on all child route items.
-        ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
-          pageTitle {
-            jsonValue
-            value
-          }
-        }
-        url {
-          path
-        }
-      }
-    }
-  }
-}
+# This file contains a GraphQL query that will be executed and the result provided to
+# your JSS component. You can run this query in GraphiQL ($endpoint/ui) for a nice editing experience.
+
+# Note that we're executing _two queries_ (datasource and contextItem)
+# within the context of the IntegratedDemoQuery _operation_. This makes it
+# very efficient at gathering data from multiple sources.
+
+query IntegratedDemoQuery($datasource: String!, $contextItem: String!, $language: String!) {
+  # Datasource query
+  # $datasource will always be set to the ID of the rendering's datasource item
+  # (as long as the GraphQLData helper is used)
+  datasource: item(path: $datasource, language: $language) {
+    id
+    name
+    # Strongly-typed querying on known templates is possible!
+    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>GraphQLIntegratedDemo {
+      # Single-line text field
+      sample1 {
+        # the 'jsonValue' field is a JSON blob that represents the object that
+        # should be passed to JSS field rendering helpers (i.e. text, image, link)
+        jsonValue
+        value
+      }
+      # General Link field
+      sample2 {
+        jsonValue
+        # Structured querying of the field's values is possible
+        text
+        target
+        url
+        # Access to the template definition is possible
+        definition {
+          type
+          shared
+        }
+      }
+    }
+  }
+
+  # Context/route item query
+  # $contextItem will always be set to the ID of the current context item (the route item)
+  # (as long as the GraphQLData helper is used)
+  contextItem: item(path: $contextItem, language: $language) {
+    id
+    # Get the page title from the app route template
+    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
+      pageTitle {
+        value
+      }
+    }
+
+    # List the children of the current route
+    children(hasLayout: true) {
+      results {
+        id
+        # typing fragments can be used anywhere!
+        # so in this case, we're grabbing the 'pageTitle'
+        # field on all child route items.
+        ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
+          pageTitle {
+            jsonValue
+            value
+          }
+        }
+        url {
+          path
+        }
+      }
+    }
+  }
+}

package/dist/templates/{angular-sxp → angular}/sitecore/gitignore

@@ -1,3 +1,3 @@
-manifest
-update-package
+manifest
+update-package
 package

package/dist/templates/angular/src/app/app.component.html

@@ -1 +1 @@
-<router-outlet></router-outlet>
+<router-outlet></router-outlet>

package/dist/templates/angular/src/app/app.module.ts

@@ -10,6 +10,7 @@ import { TranslateModule, TranslateLoader } from '@ngx-translate/core';
 import { JssTranslationClientLoaderService } from './i18n/jss-translation-client-loader.service';
 import { JssTranslationLoaderService } from './i18n/jss-translation-loader.service';
 import { GraphQLModule } from './jss-graphql.module';
+import { JssDataFetcherService } from './jss-data-fetcher.service';
 import { JssMetaService } from './jss-meta.service';
 
 @NgModule({
@@ -30,6 +31,7 @@ import { JssMetaService } from './jss-meta.service';
     // The token is needed in cases when multiple applications are bootstrapped on a page
     { provide: APP_ID, useValue: 'my-app' },
     JssContextService,
+    JssDataFetcherService,
     JssLayoutService,
     JssMetaService,
     // IMPORTANT: you must set the base href with this token, not a <base> tag in the HTML.

package/dist/templates/angular/src/app/components/app-components.shared.module.ts

@@ -3,6 +3,7 @@ import { CommonModule } from '@angular/common';
 import { FormsModule } from '@angular/forms';
 import { TranslateModule } from '@ngx-translate/core';
 import { RouterModule } from '@angular/router';
+import { StyleguideSpecimenComponent } from './shared/styleguide-specimen/styleguide-specimen.component';
 import { JssModule } from '@sitecore-jss/sitecore-jss-angular';
 
 /*
@@ -13,8 +14,22 @@ import { JssModule } from '@sitecore-jss/sitecore-jss-angular';
   Don't want code generation? See ./.gitignore for instructions to turn it off.
 */
 @NgModule({
-  imports: [CommonModule, TranslateModule, RouterModule, JssModule, FormsModule],
-  exports: [CommonModule, TranslateModule, RouterModule, FormsModule],
-  declarations: [],
+  imports: [
+    CommonModule,
+    TranslateModule,
+    RouterModule,
+    JssModule,
+    FormsModule,
+  ],
+  exports: [
+    CommonModule,
+    TranslateModule,
+    RouterModule,
+    FormsModule,
+    StyleguideSpecimenComponent
+  ],
+  declarations: [
+    StyleguideSpecimenComponent
+  ],
 })
-export class AppComponentsSharedModule {}
+export class AppComponentsSharedModule { }

package/dist/templates/angular/src/app/components/content-block/content-block.component.html

@@ -1,4 +1,4 @@
-<div class="contentBlock">
-  <h2 class="contentTitle" *scText="rendering.fields.heading"></h2>
-  <div class="contentDescription" *scRichText="rendering.fields.content"></div>
-</div>
+<div class="contentBlock">
+  <h2 class="contentTitle" *scText="rendering.fields.heading"></h2>
+  <div class="contentDescription" *scRichText="rendering.fields.content"></div>
+</div>

package/dist/templates/angular/src/app/components/gitignore

@@ -1,7 +1,7 @@
-# App component module is auto-generated by default.
-# To manually maintain the module,
-# - Remove this ignore file
-# - Delete /scripts/generate-component-factory.ts
-# - Remove the reference from /scripts/bootstrap.ts
-# - Consider merging app-components.shared and app-components modules
-app-components.module.ts
+# App component module is auto-generated by default.
+# To manually maintain the module,
+# - Remove this ignore file
+# - Delete /scripts/generate-component-factory.ts
+# - Remove the reference from /scripts/bootstrap.ts
+# - Consider merging app-components.shared and app-components modules
+app-components.module.ts

package/dist/templates/{angular-sxp → angular}/src/app/components/graph-ql-connected-demo/graph-ql-connected-demo.component.graphql

@@ -1,69 +1,69 @@
-# This file contains a GraphQL query that will be executed and the result provided to
-# your JSS component. You can run this query in GraphiQL ($endpoint/ui) for a nice editing experience.
-
-# Note that we're executing _two queries_ (datasource and contextItem)
-# within the context of the ConnectedDemoQuery _operation_. This makes it
-# very efficient at gathering data from multiple sources.
-
-query ConnectedDemoQuery($datasource: String!, $contextItem: String!, $language: String!) {
-  # Datasource query
-  # $datasource should be set to the ID of the rendering's datasource item
-  datasource: item(path: $datasource, language: $language) {
-    id
-    name
-    # Strongly-typed querying on known templates is possible!
-    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>GraphQLConnectedDemo {
-      # Single-line text field
-      sample1 {
-        # the 'jsonValue' field is a JSON blob that represents the object that
-        # should be passed to JSS field rendering helpers (i.e. text, image, link)
-        jsonValue
-        value
-      }
-      # General Link field
-      sample2 {
-        jsonValue
-        # Structured querying of the field's values is possible
-        text
-        target
-        url
-        # Access to the template definition is possible
-        definition {
-          type
-          shared
-        }
-      }
-    }
-  }
-
-  # Context/route item query
-  # $contextItem should be set to the ID of the current context item (the route item)
-  contextItem: item(path: $contextItem, language: $language) {
-    id
-    # Get the page title from the app route template
-    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
-      pageTitle {
-        value
-      }
-    }
-
-    # List the children of the current route
-    children(hasLayout: true) {
-      results {
-        id
-        # typing fragments can be used anywhere!
-        # so in this case, we're grabbing the 'pageTitle'
-        # field on all child route items.
-        ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
-          pageTitle {
-            jsonValue
-            value
-          }
-        }
-        url {
-          path
-        }
-      }
-    }
-  }
-}
+# This file contains a GraphQL query that will be executed and the result provided to
+# your JSS component. You can run this query in GraphiQL ($endpoint/ui) for a nice editing experience.
+
+# Note that we're executing _two queries_ (datasource and contextItem)
+# within the context of the ConnectedDemoQuery _operation_. This makes it
+# very efficient at gathering data from multiple sources.
+
+query ConnectedDemoQuery($datasource: String!, $contextItem: String!, $language: String!) {
+  # Datasource query
+  # $datasource should be set to the ID of the rendering's datasource item
+  datasource: item(path: $datasource, language: $language) {
+    id
+    name
+    # Strongly-typed querying on known templates is possible!
+    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>GraphQLConnectedDemo {
+      # Single-line text field
+      sample1 {
+        # the 'jsonValue' field is a JSON blob that represents the object that
+        # should be passed to JSS field rendering helpers (i.e. text, image, link)
+        jsonValue
+        value
+      }
+      # General Link field
+      sample2 {
+        jsonValue
+        # Structured querying of the field's values is possible
+        text
+        target
+        url
+        # Access to the template definition is possible
+        definition {
+          type
+          shared
+        }
+      }
+    }
+  }
+
+  # Context/route item query
+  # $contextItem should be set to the ID of the current context item (the route item)
+  contextItem: item(path: $contextItem, language: $language) {
+    id
+    # Get the page title from the app route template
+    ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
+      pageTitle {
+        value
+      }
+    }
+
+    # List the children of the current route
+    children(hasLayout: true) {
+      results {
+        id
+        # typing fragments can be used anywhere!
+        # so in this case, we're grabbing the 'pageTitle'
+        # field on all child route items.
+        ...on <%- helper.getAppPrefix(appPrefix, appName, false) %>AppRoute {
+          pageTitle {
+            jsonValue
+            value
+          }
+        }
+        url {
+          path
+        }
+      }
+    }
+  }
+}