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

package/dist/templates/angular/data/routes/graphql/en.yml

@@ -1,27 +1,27 @@
-fields:
-  pageTitle: GraphQL | Sitecore JSS
-placeholders:
-  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
-    - componentName: ContentBlock
-      fields:
-        heading: Using GraphQL with JSS
-        content: |
-          <p>This is a live example of using Integrated GraphQL and Connected GraphQL with a JSS app.
-          For more information on GraphQL use in JSS, please see <a href="https://jss.sitecore.com" target="_blank" rel="noopener noreferrer">the documentation</a>.</p>
-    - componentName: GraphQLLayout
-      placeholders:
-        <%- helper.getAppPrefix(appPrefix, appName) %>jss-graphql-layout:
-          - componentName: GraphQLIntegratedDemo
-            fields:
-              sample1: Hello integrated GraphQL world!
-              sample2:
-                href: https://www.sitecore.com
-                target: _blank
-                text: GraphQL lets you get structured field data too
-          - componentName: GraphQLConnectedDemo
-            fields:
-              sample1: Hello connected GraphQL world!
-              sample2:
-                href: https://www.sitecore.com
-                target: _blank
-                text: GraphQL lets you get structured field data too
+fields:
+  pageTitle: GraphQL | Sitecore JSS
+placeholders:
+  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
+    - componentName: ContentBlock
+      fields:
+        heading: Using GraphQL with JSS
+        content: |
+          <p>This is a live example of using Integrated GraphQL and Connected GraphQL with a JSS app.
+          For more information on GraphQL use in JSS, please see <a href="https://jss.sitecore.com" target="_blank" rel="noopener noreferrer">the documentation</a>.</p>
+    - componentName: GraphQLLayout
+      placeholders:
+        <%- helper.getAppPrefix(appPrefix, appName) %>jss-graphql-layout:
+          - componentName: GraphQLIntegratedDemo
+            fields:
+              sample1: Hello integrated GraphQL world!
+              sample2:
+                href: https://www.sitecore.com
+                target: _blank
+                text: GraphQL lets you get structured field data too
+          - componentName: GraphQLConnectedDemo
+            fields:
+              sample1: Hello connected GraphQL world!
+              sample2:
+                href: https://www.sitecore.com
+                target: _blank
+                text: GraphQL lets you get structured field data too

package/dist/templates/angular/data/routes/graphql/sample-1/en.yml

@@ -1,9 +1,9 @@
-fields:
-  pageTitle: Sample 1 Page Title
-placeholders:
-  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
-    - componentName: ContentBlock
-      fields:
-        heading: GraphQL Sample 1
-        content: |
-          <p>A child route here to illustrate the power of GraphQL queries. <a href="/graphql">Back to GraphQL route</a></p>
+fields:
+  pageTitle: Sample 1 Page Title
+placeholders:
+  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
+    - componentName: ContentBlock
+      fields:
+        heading: GraphQL Sample 1
+        content: |
+          <p>A child route here to illustrate the power of GraphQL queries. <a href="/graphql">Back to GraphQL route</a></p>

package/dist/templates/angular/data/routes/graphql/sample-2/en.yml

@@ -1,9 +1,9 @@
-fields:
-  pageTitle: Sample 2 Page Title
-placeholders:
-  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
-    - componentName: ContentBlock
-      fields:
-        heading: GraphQL Sample 2
-        content: |
-          <p>A child route here to illustrate the power of GraphQL queries. <a href="/graphql">Back to GraphQL route</a></p>
+fields:
+  pageTitle: Sample 2 Page Title
+placeholders:
+  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
+    - componentName: ContentBlock
+      fields:
+        heading: GraphQL Sample 2
+        content: |
+          <p>A child route here to illustrate the power of GraphQL queries. <a href="/graphql">Back to GraphQL route</a></p>

package/dist/templates/angular/data/routes/styleguide/custom-route-type/en.yml

@@ -1,12 +1,12 @@
-# Using a Custom Route Type enables adding more field data to the route level.
-template: <%- helper.getAppPrefix(appPrefix, appName) %>ExampleCustomRouteType
-fields:
-  # Note that custom route types inherit from the default route type automatically.
-  # This is what makes the `pageTitle` field available here, when it's not defined on the custom route type.
-  pageTitle: Custom Route Type | Sitecore JSS
-  headline: A Treatise on Route-Level Fields in JSS
-  author: Myrtle
-  content: <p>Custom route type fields are good for things like articles, where you may wish to have a filter UI on content fields, such as author or category. Route level fields are easy to query against, whereas component-level fields are not because it's possible to remove a component from a route. Note that route level fields <em>cannot be personalized</em> because you cannot conditionally swap out the route item for a different content item.</p>
-placeholders:
-  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
-    - componentName: StyleguideCustomRouteType
+# Using a Custom Route Type enables adding more field data to the route level.
+template: <%- helper.getAppPrefix(appPrefix, appName) %>ExampleCustomRouteType
+fields:
+  # Note that custom route types inherit from the default route type automatically.
+  # This is what makes the `pageTitle` field available here, when it's not defined on the custom route type.
+  pageTitle: Custom Route Type | Sitecore JSS
+  headline: A Treatise on Route-Level Fields in JSS
+  author: Myrtle
+  content: <p>Custom route type fields are good for things like articles, where you may wish to have a filter UI on content fields, such as author or category. Route level fields are easy to query against, whereas component-level fields are not because it's possible to remove a component from a route. Note that route level fields <em>cannot be personalized</em> because you cannot conditionally swap out the route item for a different content item.</p>
+placeholders:
+  <%- helper.getAppPrefix(appPrefix, appName) %>jss-main:
+    - componentName: StyleguideCustomRouteType