create-sitecore-jss 22.2.1-canary.3 → 22.2.1

package/dist/templates/angular/src/app/components/styleguide-layout-reuse/styleguide-layout-reuse.component.html

@@ -1,52 +1,52 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-layout-reuse">
-  <!--
-      This placeholder is:
-      - Using the `sc-placeholder` attribute to avoid rendering a wrapping tag of its own, so that Bootstrap's columns will work
-          (.row > sc-placeholder > .col-sm will not layout with flexbox, but .row > .col-sm will)
-      - Using templating to enable customizing the markup for each component within. In this case, it's placing each component
-        in its own column of a flexbox layout - giving an n-up columnar layout. The component itself does not need to know that
-        it's living in a columnar layout.
-    -->
-  <div
-    class="row"
-    sc-placeholder
-    name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-reuse-example"
-    [rendering]="rendering"
-  >
-    <!--
-        Customized component rendering
-        You can customize the rendering of each component in this placeholder using the renderEach template.
-        This technique is useful for things like flexible column layouts (like this one), or to wrap each component
-        in <li>, or otherwise alter the component rendering from outside the component itself.
-
-        If you need to know the index of the rendering, you can add 'let-index="index"' to the ng-template
-        Remove the template entirely to use default component rendering (no wrappers, etc)
-      -->
-    <ng-template renderEach let-rendering="rendering">
-      <div class="col-sm">
-        <!-- renders a single component like a placeholder does, based on the component data -->
-        <sc-render-component [rendering]="rendering"></sc-render-component>
-      </div>
-    </ng-template>
-    <!--
-        Customized empty placeholder rendering
-        When using renderEach, in some situations an _empty placeholder_ (with no components in it)
-        may not be editable in the Sitecore Experience Editor. In this example, because of the use
-        of flexbox by the bootstrap columns, adding a bare <div> for the selectable empty placeholder
-        results in it being hidden as it does not have a column class.
-
-        Using the renderEmpty template allows us to customize the rendering of an empty placeholder
-        and place it within a column div so that we can select it correctly.
-      -->
-    <ng-template renderEmpty let-renderings="renderings">
-      <div class="col-sm">
-        <!--
-            The empty placeholder is rendered with another sc-placeholder, but using the
-            renderings (plural) input instead of rendering. In this mode, it accepts a
-            raw component data array, and name is unnecessary.
-          -->
-        <sc-placeholder [renderings]="renderings"></sc-placeholder>
-      </div>
-    </ng-template>
-  </div>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-layout-reuse">
+  <!--
+      This placeholder is:
+      - Using the `sc-placeholder` attribute to avoid rendering a wrapping tag of its own, so that Bootstrap's columns will work
+          (.row > sc-placeholder > .col-sm will not layout with flexbox, but .row > .col-sm will)
+      - Using templating to enable customizing the markup for each component within. In this case, it's placing each component
+        in its own column of a flexbox layout - giving an n-up columnar layout. The component itself does not need to know that
+        it's living in a columnar layout.
+    -->
+  <div
+    class="row"
+    sc-placeholder
+    name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-reuse-example"
+    [rendering]="rendering"
+  >
+    <!--
+        Customized component rendering
+        You can customize the rendering of each component in this placeholder using the renderEach template.
+        This technique is useful for things like flexible column layouts (like this one), or to wrap each component
+        in <li>, or otherwise alter the component rendering from outside the component itself.
+
+        If you need to know the index of the rendering, you can add 'let-index="index"' to the ng-template
+        Remove the template entirely to use default component rendering (no wrappers, etc)
+      -->
+    <ng-template renderEach let-rendering="rendering">
+      <div class="col-sm">
+        <!-- renders a single component like a placeholder does, based on the component data -->
+        <sc-render-component [rendering]="rendering"></sc-render-component>
+      </div>
+    </ng-template>
+    <!--
+        Customized empty placeholder rendering
+        When using renderEach, in some situations an _empty placeholder_ (with no components in it)
+        may not be editable in the Sitecore Experience Editor. In this example, because of the use
+        of flexbox by the bootstrap columns, adding a bare <div> for the selectable empty placeholder
+        results in it being hidden as it does not have a column class.
+
+        Using the renderEmpty template allows us to customize the rendering of an empty placeholder
+        and place it within a column div so that we can select it correctly.
+      -->
+    <ng-template renderEmpty let-renderings="renderings">
+      <div class="col-sm">
+        <!--
+            The empty placeholder is rendered with another sc-placeholder, but using the
+            renderings (plural) input instead of rendering. In this mode, it accepts a
+            raw component data array, and name is unnecessary.
+          -->
+        <sc-placeholder [renderings]="renderings"></sc-placeholder>
+      </div>
+    </ng-template>
+  </div>
+</app-styleguide-specimen>

package/dist/templates/angular/src/app/components/styleguide-layout-tabs/styleguide-layout-tabs.component.html

@@ -1,37 +1,37 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-layout-tabs">
-  <!--
-    When the page is editing, we hide the tab headings, because they are not updated when xEditor adds or removes a tab rendering.
-    Instead, we show the tab header inline with the tab contents (see styleguide-layout-tabs-tab).
-  -->
-  <ul class="nav nav-tabs" *ngIf="!isEditing">
-    <li class="nav-item" *ngFor="let tab of tabs">
-      <a
-        [ngClass]="{ 'nav-link': true, active: tab === activeTab }"
-        (click)="activeTab = tab; (false)"
-        href="#"
-      >
-        <span *scText="tab.fields.title"></span>
-      </a>
-    </li>
-  </ul>
-  <div class="p-3 border-left border-right border-bottom">
-    <ng-container *ngIf="isEditing">
-      <!--
-        When experience editor is active we want to render all tabs in a stack,
-        to simplify editing.
-      -->
-      <sc-placeholder
-        name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-tabs"
-        [rendering]="rendering"
-      ></sc-placeholder>
-    </ng-container>
-    <ng-container *ngIf="!isEditing">
-      <!--
-        We only want to render the _active_ tab when we're not editing.
-        sc-render-component renders a _single_ component given its data,
-        allowing us to partially render the placeholder contents.
-      -->
-      <sc-render-component [rendering]="activeTab"></sc-render-component>
-    </ng-container>
-  </div>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-layout-tabs">
+  <!--
+    When the page is editing, we hide the tab headings, because they are not updated when xEditor adds or removes a tab rendering.
+    Instead, we show the tab header inline with the tab contents (see styleguide-layout-tabs-tab).
+  -->
+  <ul class="nav nav-tabs" *ngIf="!isEditing">
+    <li class="nav-item" *ngFor="let tab of tabs">
+      <a
+        [ngClass]="{ 'nav-link': true, active: tab === activeTab }"
+        (click)="activeTab = tab; (false)"
+        href="#"
+      >
+        <span *scText="tab.fields.title"></span>
+      </a>
+    </li>
+  </ul>
+  <div class="p-3 border-left border-right border-bottom">
+    <ng-container *ngIf="isEditing">
+      <!--
+        When experience editor is active we want to render all tabs in a stack,
+        to simplify editing.
+      -->
+      <sc-placeholder
+        name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-tabs"
+        [rendering]="rendering"
+      ></sc-placeholder>
+    </ng-container>
+    <ng-container *ngIf="!isEditing">
+      <!--
+        We only want to render the _active_ tab when we're not editing.
+        sc-render-component renders a _single_ component given its data,
+        allowing us to partially render the placeholder contents.
+      -->
+      <sc-render-component [rendering]="activeTab"></sc-render-component>
+    </ng-container>
+  </div>
+</app-styleguide-specimen>

package/dist/templates/angular/src/app/components/styleguide-layout-tabs-tab/styleguide-layout-tabs-tab.component.html

@@ -1,12 +1,12 @@
-<!--
-  When we're editing the tabs we stack each tab vertically,
-  which means there's no regular tab titles rendered.
-  So we conditionally render the tab title here, when editing.
--->
-<div data-e2e-class="styleguide-layout-tabs-tab">
-  <ng-container *ngIf="isEditing">
-    <h5 *scText="rendering.fields.title"></h5>
-  </ng-container>
-
-  <div *scRichText="rendering.fields.content"></div>
-</div>
+<!--
+  When we're editing the tabs we stack each tab vertically,
+  which means there's no regular tab titles rendered.
+  So we conditionally render the tab title here, when editing.
+-->
+<div data-e2e-class="styleguide-layout-tabs-tab">
+  <ng-container *ngIf="isEditing">
+    <h5 *scText="rendering.fields.title"></h5>
+  </ng-container>
+
+  <div *scRichText="rendering.fields.content"></div>
+</div>

package/dist/templates/angular/src/app/components/styleguide-multilingual/styleguide-multilingual.component.html

@@ -1,15 +1,15 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-multilingual">
-  <p *scText="rendering.fields.sample; encode: false;"></p>
-
-  <p>
-    This is a static dictionary entry from <code>/data/dictionary</code>: {{ 'styleguide-sample' | translate }}
-  </p>
-
-  <p>
-    <a routerLink="/en/styleguide" (click)="switchLanguage($event)">Show in English</a>
-    <br />
-    <a routerLink="/<%- language %>/styleguide" (click)="switchLanguage($event)">Show in <%- language %></a>
-  </p>
-
-  <p>The current language is: {{ translate.currentLang }}</p>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-multilingual">
+  <p *scText="rendering.fields.sample; encode: false;"></p>
+
+  <p>
+    This is a static dictionary entry from <code>/data/dictionary</code>: {{ 'styleguide-sample' | translate }}
+  </p>
+
+  <p>
+    <a routerLink="/en/styleguide" (click)="switchLanguage($event)">Show in English</a>
+    <br />
+    <a routerLink="/<%- language %>/styleguide" (click)="switchLanguage($event)">Show in <%- language %></a>
+  </p>
+
+  <p>The current language is: {{ translate.currentLang }}</p>
+</app-styleguide-specimen>

package/dist/templates/angular/src/app/components/styleguide-route-fields/styleguide-route-fields.component.html

@@ -1,8 +1,8 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-route-fields">
-  Route level <code>pageTitle</code> field:
-  <span *scText="contextFields.pageTitle"></span>
-
-  <p>
-    <a routerLink="/styleguide/custom-route-type">Sample of using a custom route type</a>
-  </p>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-route-fields">
+  Route level <code>pageTitle</code> field:
+  <span *scText="contextFields.pageTitle"></span>
+
+  <p>
+    <a routerLink="/styleguide/custom-route-type">Sample of using a custom route type</a>
+  </p>
+</app-styleguide-specimen>

package/dist/templates/angular/src/app/components/styleguide-section/styleguide-section.component.html

@@ -1,7 +1,7 @@
-<div class="pt-3" [id]="id">
-  <h3 class="border-bottom" *scText="rendering.fields.heading"></h3>
-  <sc-placeholder
-    name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-styleguide-section"
-    [rendering]="rendering"
-  ></sc-placeholder>
-</div>
+<div class="pt-3" [id]="id">
+  <h3 class="border-bottom" *scText="rendering.fields.heading"></h3>
+  <sc-placeholder
+    name="<%- helper.getAppPrefix(appPrefix, appName) %>jss-styleguide-section"
+    [rendering]="rendering"
+  ></sc-placeholder>
+</div>

package/dist/templates/angular/src/app/components/styleguide-sitecore-context/styleguide-sitecore-context.component.html

@@ -1,3 +1,3 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-sitecore-context">
-    <p>The current Sitecore Context has been logged to the console.</p>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-sitecore-context">
+    <p>The current Sitecore Context has been logged to the console.</p>
+</app-styleguide-specimen>

package/dist/templates/angular/src/app/components/styleguide-tracking/styleguide-tracking.component.html

@@ -1,175 +1,175 @@
-<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-tracking">
-  <p *ngIf="disconnectedMode">The tracking API is only available in connected, integrated, or headless modes.</p>
-
-  <div *ngIf="!disconnectedMode">
-    <p class="alert alert-warning">
-      Note: The JSS tracker API is disabled by default. Consult the <a href="https://jss.sitecore.com/docs/fundamentals/services/tracking">tracking documentation</a> to enable it.
-    </p>
-    <div class="row">
-      <fieldset class="form-group col-sm">
-        <legend>Event</legend>
-        <p>
-          Events are defined in <code>/sitecore/system/Settings/Analytics/Page Events</code>
-        </p>
-        <label htmlFor="event">Event GUID or Name</label>
-        <input type="text" id="event" class="form-control" [(ngModel)]="event" />
-        <button
-          type="button"
-          class="btn btn-primary mt-3"
-          (click)="submitEvent()"
-        >
-          Submit
-        </button>
-      </fieldset>
-
-      <fieldset class="form-group col-sm">
-        <legend>Goal</legend>
-        <p>
-          Goals are defined in <code>/sitecore/system/Marketing Control Panel/Goals</code>
-        </p>
-        <label htmlFor="goal">Goal GUID or Name</label>
-        <input
-          type="text"
-          class="form-control"
-          id="goal"
-          name="goal"
-          [(ngModel)]="goal"
-          placeholder="i.e. Register"
-        />
-        <button
-          type="button"
-          class="btn btn-primary mt-3"
-          (click)="submitGoal()"
-        >
-          Submit
-        </button>
-      </fieldset>
-    </div>
-    <div class="row">
-      <fieldset class="form-group col-sm">
-        <legend>Outcome</legend>
-        <p>
-          Outcomes are defined in <code>/sitecore/system/Marketing Control Panel/Outcomes</code>
-        </p>
-        <label htmlFor="outcomeName">Outcome GUID or Name</label>
-        <input
-          type="text"
-          class="form-control"
-          id="outcomeName"
-          name="outcomeName"
-          [(ngModel)]="outcomeName"
-          placeholder="i.e. Marketing Lead"
-        />
-        <br />
-        <label htmlFor="outcomeValue">Monetary Value (optional)</label>
-        <input
-          type="number"
-          class="form-control"
-          id="outcomeValue"
-          name="outcomeValue"
-          [(ngModel)]="outcomeValue"
-          placeholder="i.e. 1337.00"
-        />
-        <button
-          type="button"
-          class="btn btn-primary mt-3"
-          (click)="submitOutcome()"
-        >
-          Submit
-        </button>
-      </fieldset>
-
-      <fieldset class="form-group col-sm">
-        <legend>Campaign</legend>
-        <p>
-          Campaigns are defined in <code>/sitecore/system/Marketing Control Panel/Campaigns</code>
-        </p>
-        <label htmlFor="campaign">Campaign GUID or Name</label>
-        <input type="text" class="form-control" id="campaign" [(ngModel)]="campaign" />
-        <button
-          type="button"
-          class="btn btn-primary mt-3"
-          (click)="triggerCampaign()"
-        >
-          Submit
-        </button>
-      </fieldset>
-    </div>
-    <div class="row">
-      <fieldset class="form-group col-sm">
-        <legend>Page View</legend>
-        <p>
-          Track arbitrary page views for custom routing or offline use. Note that Layout
-          Service tracks page views by default unless <code>tracking=false</code> is passed
-          in its query string.
-        </p>
-        <label htmlFor="pageId">Page Item GUID</label>
-        <input
-          type="text"
-          class="form-control"
-          id="pageId"
-          name="pageId"
-          [(ngModel)]="pageId"
-          placeholder="i.e. 11111111-1111-1111-1111-111111111111"
-        />
-        <br />
-        <label htmlFor="pageUrl">Page URL</label>
-        <input
-          type="text"
-          class="form-control"
-          id="pageUrl"
-          name="pageUrl"
-          [(ngModel)]="pageUrl"
-          placeholder="i.e. /foo/bar"
-        />
-        <button
-          type="button"
-          class="btn btn-primary mt-3"
-          (click)="submitPageView()"
-        >
-          Submit
-        </button>
-      </fieldset>
-
-      <fieldset class="form-group col-sm">
-        <legend>Batching</legend>
-        <p>
-          The tracking API supports pushing a whole batch of events in a single request.
-          This can be useful for queuing strategies or offline PWA usage.
-        </p>
-        <button
-          type="button"
-          class="btn btn-primary"
-          (click)="submitBatching()"
-        >
-          Submit Batch of Events
-        </button>
-      </fieldset>
-    </div>
-    <div class="row">
-      <fieldset class="form-group col-sm">
-        <legend>Interaction Control</legend>
-        <p>
-          Tracking data is not pushed into the xConnect service until your session ends on
-          the Sitecore server. Click this button to instantly end your session and flush the
-          data - great for debugging and testing.
-        </p>
-        <p class="alert alert-warning">
-          Note: By default <em>anonymous</em> contacts will not be shown in Experience
-          Profile. If your interactions are not showing up in Experience Profile, you may
-          need to
-          <a href="https://doc.sitecore.net/developers/xp/xconnect/xconnect-search-indexer/enable-anonymous-contact-indexing.html">
-            enable anonymous contact indexing.
-          </a>
-        </p>
-        <button
-          type="button"
-          class="btn btn-primary"
-          (click)="abandonSession()"
-        >
-          End Interaction
-        </button>
-      </fieldset>
-    </div>
-  </div>
-</app-styleguide-specimen>
+<app-styleguide-specimen [rendering]="rendering" e2eId="styleguide-tracking">
+  <p *ngIf="disconnectedMode">The tracking API is only available in connected, integrated, or headless modes.</p>
+
+  <div *ngIf="!disconnectedMode">
+    <p class="alert alert-warning">
+      Note: The JSS tracker API is disabled by default. Consult the <a href="https://jss.sitecore.com/docs/fundamentals/services/tracking">tracking documentation</a> to enable it.
+    </p>
+    <div class="row">
+      <fieldset class="form-group col-sm">
+        <legend>Event</legend>
+        <p>
+          Events are defined in <code>/sitecore/system/Settings/Analytics/Page Events</code>
+        </p>
+        <label htmlFor="event">Event GUID or Name</label>
+        <input type="text" id="event" class="form-control" [(ngModel)]="event" />
+        <button
+          type="button"
+          class="btn btn-primary mt-3"
+          (click)="submitEvent()"
+        >
+          Submit
+        </button>
+      </fieldset>
+
+      <fieldset class="form-group col-sm">
+        <legend>Goal</legend>
+        <p>
+          Goals are defined in <code>/sitecore/system/Marketing Control Panel/Goals</code>
+        </p>
+        <label htmlFor="goal">Goal GUID or Name</label>
+        <input
+          type="text"
+          class="form-control"
+          id="goal"
+          name="goal"
+          [(ngModel)]="goal"
+          placeholder="i.e. Register"
+        />
+        <button
+          type="button"
+          class="btn btn-primary mt-3"
+          (click)="submitGoal()"
+        >
+          Submit
+        </button>
+      </fieldset>
+    </div>
+    <div class="row">
+      <fieldset class="form-group col-sm">
+        <legend>Outcome</legend>
+        <p>
+          Outcomes are defined in <code>/sitecore/system/Marketing Control Panel/Outcomes</code>
+        </p>
+        <label htmlFor="outcomeName">Outcome GUID or Name</label>
+        <input
+          type="text"
+          class="form-control"
+          id="outcomeName"
+          name="outcomeName"
+          [(ngModel)]="outcomeName"
+          placeholder="i.e. Marketing Lead"
+        />
+        <br />
+        <label htmlFor="outcomeValue">Monetary Value (optional)</label>
+        <input
+          type="number"
+          class="form-control"
+          id="outcomeValue"
+          name="outcomeValue"
+          [(ngModel)]="outcomeValue"
+          placeholder="i.e. 1337.00"
+        />
+        <button
+          type="button"
+          class="btn btn-primary mt-3"
+          (click)="submitOutcome()"
+        >
+          Submit
+        </button>
+      </fieldset>
+
+      <fieldset class="form-group col-sm">
+        <legend>Campaign</legend>
+        <p>
+          Campaigns are defined in <code>/sitecore/system/Marketing Control Panel/Campaigns</code>
+        </p>
+        <label htmlFor="campaign">Campaign GUID or Name</label>
+        <input type="text" class="form-control" id="campaign" [(ngModel)]="campaign" />
+        <button
+          type="button"
+          class="btn btn-primary mt-3"
+          (click)="triggerCampaign()"
+        >
+          Submit
+        </button>
+      </fieldset>
+    </div>
+    <div class="row">
+      <fieldset class="form-group col-sm">
+        <legend>Page View</legend>
+        <p>
+          Track arbitrary page views for custom routing or offline use. Note that Layout
+          Service tracks page views by default unless <code>tracking=false</code> is passed
+          in its query string.
+        </p>
+        <label htmlFor="pageId">Page Item GUID</label>
+        <input
+          type="text"
+          class="form-control"
+          id="pageId"
+          name="pageId"
+          [(ngModel)]="pageId"
+          placeholder="i.e. 11111111-1111-1111-1111-111111111111"
+        />
+        <br />
+        <label htmlFor="pageUrl">Page URL</label>
+        <input
+          type="text"
+          class="form-control"
+          id="pageUrl"
+          name="pageUrl"
+          [(ngModel)]="pageUrl"
+          placeholder="i.e. /foo/bar"
+        />
+        <button
+          type="button"
+          class="btn btn-primary mt-3"
+          (click)="submitPageView()"
+        >
+          Submit
+        </button>
+      </fieldset>
+
+      <fieldset class="form-group col-sm">
+        <legend>Batching</legend>
+        <p>
+          The tracking API supports pushing a whole batch of events in a single request.
+          This can be useful for queuing strategies or offline PWA usage.
+        </p>
+        <button
+          type="button"
+          class="btn btn-primary"
+          (click)="submitBatching()"
+        >
+          Submit Batch of Events
+        </button>
+      </fieldset>
+    </div>
+    <div class="row">
+      <fieldset class="form-group col-sm">
+        <legend>Interaction Control</legend>
+        <p>
+          Tracking data is not pushed into the xConnect service until your session ends on
+          the Sitecore server. Click this button to instantly end your session and flush the
+          data - great for debugging and testing.
+        </p>
+        <p class="alert alert-warning">
+          Note: By default <em>anonymous</em> contacts will not be shown in Experience
+          Profile. If your interactions are not showing up in Experience Profile, you may
+          need to
+          <a href="https://doc.sitecore.net/developers/xp/xconnect/xconnect-search-indexer/enable-anonymous-contact-indexing.html">
+            enable anonymous contact indexing.
+          </a>
+        </p>
+        <button
+          type="button"
+          class="btn btn-primary"
+          (click)="abandonSession()"
+        >
+          End Interaction
+        </button>
+      </fieldset>
+    </div>
+  </div>
+</app-styleguide-specimen>