Merge pull request SharePoint#9401 from HarminderSethi/main

andrewconnell · web-flow · commit d8232ffaa33e · 2023-12-20T09:09:00.000-05:00
changes related to $schema refererence update related to SPFx 1.18.x
diff --git a/docs/spfx/debug-modern-pages.md b/docs/spfx/debug-modern-pages.md
@@ -1,7 +1,7 @@
 ---
 title: Debug SharePoint Framework solutions on modern SharePoint pages
 description: Guidance on how to debug SharePoint Framework solutions on modern SharePoint pages
-ms.date: 02/10/2022
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 # Debug SharePoint Framework solutions on modern SharePoint pages
@@ -25,7 +25,7 @@ When you add a new SharePoint Framework extension to your project, the SharePoin
 
 ```json
 {
-  "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+  "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
   "port": 4321,
   "https": true,
   "serveConfigurations": {
diff --git a/docs/spfx/extensions/get-started/build-a-hello-world-extension.md b/docs/spfx/extensions/get-started/build-a-hello-world-extension.md
@@ -1,7 +1,7 @@
 ---
 title: Build your first SharePoint Framework Extension (Hello World part 1)
 description: Create an extension project, and then code and debug your Application Customizer.
-ms.date: 06/13/2022
+ms.date: 12/4/2023
 ms.localizationpriority: high
 ms.custom: scenarios:getting-started
 ---
@@ -143,7 +143,7 @@ You can't use the SharePoint Workbench to test SharePoint Framework Extensions.
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "serveConfigurations": {
diff --git a/docs/spfx/extensions/get-started/building-form-customizer.md b/docs/spfx/extensions/get-started/building-form-customizer.md
@@ -1,7 +1,7 @@
 ---
 title: Build your first Form customizer extension
 description: Form customizers are SharePoint Framework components giving you an option to override the form experience in a list or library level by associating the component to the used content type.
-ms.date: 07/21/2022
+ms.date: 12/14/2023
 ms.custom: scenarios:getting-started
 ---
 
@@ -124,7 +124,7 @@ You can test and debug your Form Customizer within a live SharePoint Online site
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "serveConfigurations": {
diff --git a/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md b/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
@@ -1,7 +1,7 @@
 ---
 title: Build your first ListView Command Set extension
 description: Create an extension project, and then code and debug your extension by using SharePoint Framework (SPFx) Extensions.
-ms.date: 11/22/2022
+ms.date: 12/14/2023
 ms.custom: scenarios:getting-started
 ---
 # Build your first ListView Command Set extension
@@ -150,7 +150,7 @@ You cannot currently use the local Workbench to test SharePoint Framework Extens
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "serveConfigurations": {
diff --git a/docs/spfx/extensions/get-started/building-simple-field-customizer.md b/docs/spfx/extensions/get-started/building-simple-field-customizer.md
@@ -1,7 +1,7 @@
 ---
 title: Build your first Field Customizer extension
 description: Extensions are client-side components that run inside the context of a SharePoint page. Extensions can be deployed to SharePoint Online, and you can use modern JavaScript tools and libraries to build them.
-ms.date: 11/22/2022
+ms.date: 12/14/2023
 ms.custom: scenarios:getting-started
 ---
 
@@ -128,7 +128,7 @@ You can't use the local Workbench to test SharePoint Framework Extensions. You n
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "serveConfigurations": {
diff --git a/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md b/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md
@@ -1,7 +1,7 @@
 ---
 title: Use page placeholders from Application Customizer (Hello World part 2)
 description: Extend your Hello World extension to take advantage of page placeholders by using SharePoint Framework (SPFx) Extensions.
-ms.date: 06/07/2022
+ms.date: 12/14/2023
 ms.custom: scenarios:getting-started
 ---
 
@@ -250,7 +250,7 @@ You're now ready to test your code in SharePoint Online.
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "serveConfigurations": {
diff --git a/docs/spfx/viva/features/focus-feature/FocusFeatureTutorial.md b/docs/spfx/viva/features/focus-feature/FocusFeatureTutorial.md
@@ -1,7 +1,7 @@
 ---
 title: Create an Adaptive Card Extension with the focus feature
 description: Step by step guide on how to create an Adaptive Card Extension with the focus feature.
-ms.date: 04/04/2023
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 # Create an Adaptive Card Extension with focus feature
@@ -66,7 +66,7 @@ When you use the gulp task **serve**, by default it will launch a browser with t
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "initialPage": "https://{tenantDomain}/_layouts/workbench.aspx"
diff --git a/docs/spfx/viva/get-started/actions/geolocation/GeolocationTutorial.md b/docs/spfx/viva/get-started/actions/geolocation/GeolocationTutorial.md
@@ -1,7 +1,7 @@
 ---
 title: Create an Adaptive Card Extension with geolocation action
 description: Step by step guide on creating Adaptive Card Extension for Geolocation action.
-ms.date: 09/12/2023
+ms.date: 12/15/2023
 ms.localizationpriority: high
 ---
 # Create an Adaptive Card Extension with geolocation action
@@ -39,7 +39,7 @@ When you use the gulp task **serve**, by default it will launch a browser with t
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "initialPage": "https://{tenantDomain}/_layouts/workbench.aspx"
@@ -199,7 +199,7 @@ With this, we are providing two text-blocks to show the **Latitude** and **Longi
 
 After adding these actions, your Quick View would look like:
 
-![Card appearance after introducing changes in the quick-view](../../../../../../docs/images/viva-extensibility/geolocation/geoloactionQuickView.png)
+![Card appearance after adding actions in the quick-view](../../../../../../docs/images/viva-extensibility/geolocation/geoloactionQuickView.png)
 
 ### Set up the state for our Adaptive Card Extension
 
diff --git a/docs/spfx/viva/get-started/actions/media-upload/MediaUploadTutorial.md b/docs/spfx/viva/get-started/actions/media-upload/MediaUploadTutorial.md
@@ -1,7 +1,7 @@
 ---
 title: Create an Adaptive Card Extension with the select media action
 description: Step by step guide on how to create an Adaptive Card Extension with the select media action.
-ms.date: 03/08/2023
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 # Create an Adaptive Card Extension with select media action
@@ -34,7 +34,7 @@ When you use the gulp task **serve**, by default it will launch a browser with t
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "initialPage": "https://{tenantDomain}/_layouts/workbench.aspx"
diff --git a/docs/spfx/viva/get-started/build-first-sharepoint-adaptive-card-extension.md b/docs/spfx/viva/get-started/build-first-sharepoint-adaptive-card-extension.md
@@ -1,7 +1,7 @@
 ---
 title: Build your first SharePoint Adaptive Card Extension
 description: Adaptive Card Extensions (ACEs) are a new SharePoint Framework component type, which enable developers to build rich, native extensions to Viva Connections' Dashboards and SharePoint Pages. In this tutorial, you'll build and explore your first ACE.
-ms.date: 09/12/2023
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 # Build your first SharePoint Adaptive Card Extension
@@ -39,7 +39,7 @@ When you use the gulp task **serve**, by default it will launch a browser with t
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "initialPage": "https://{tenantDomain}/_layouts/workbench.aspx"
@@ -192,7 +192,7 @@ As part of the `cardViewParameters` property, you can specify the following:
 - **footer**: Footer components for the card view.
 
 > [!NOTE]
-> The card views for Adaptive Card templates are limited to predefined [permutations](../permutations) and cannot be changed. The parameters type (`ComponentsCardViewParameters`) is defined to only accept the properties that are supported by the permutations.
+> The card views for Adaptive Card templates are limited to predefined [permutations](../design/designing-card.md) and cannot be changed. The parameters type (`ComponentsCardViewParameters`) is defined to only accept the properties that are supported by the permutations.
 
 Additionally, there are two generics for the `properties` and `state` objects shared between the view and the ACE.
 
diff --git a/docs/spfx/viva/get-started/build-people-search-adaptive-card-extension.md b/docs/spfx/viva/get-started/build-people-search-adaptive-card-extension.md
@@ -1,7 +1,7 @@
 ---
 title: Create a People Search Adaptive Card Extension
 description: Step by step guide on creating People Search Adaptive Card Extension.
-ms.date: 06/28/2023
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 # Create a People Search Adaptive Card Extension
@@ -48,7 +48,7 @@ When you use the gulp task **serve**, by default it opens a browser with the spe
 
     ```json
     {
-      "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+      "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
       "port": 4321,
       "https": true,
       "initialPage": "https://{tenantDomain}/ _layouts/workbench.aspx"
diff --git a/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md b/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
@@ -1,7 +1,7 @@
 ---
 title: Use @pnp/sp (PnPJS) library with SharePoint Framework web parts
 description: This library provides a fluent API to make building your REST queries intuitive and supports batching and caching.
-ms.date: 06/22/2023
+ms.date: 12/14/2023
 ms.localizationpriority: high
 ---
 
@@ -59,7 +59,7 @@ You can download the [full source](https://github.com/pnp/sp-dev-fx-webparts/tre
 
 ```json
 {
-  "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
+  "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/spfx-serve.schema.json",
   "port": 4321,
   "https": true,
   "initialPage": "https://{your tenant name}/sites/dev/_layouts/15/workbench.aspx"
