Update ts fenced code blocs to typescript

- references SharePoint#5926

Author: andrewconnell

docs/spfx/connect-to-anonymous-apis.md

@@ -17,7 +17,7 @@ When building SharePoint Framework solutions, you might want to consume public A
 
 The easiest way, to connect to anonymous APIs in your SharePoint Framework solutions, is by using the HttpClient provided as a part of the SharePoint Framework. For example, to get dummy information from the Typicode service, you would execute:
 
-```ts
+```typescript
 this.context.httpClient
   .get('https://jsonplaceholder.typicode.com/todos/1', HttpClient.configurations.v1)
   .then((res: HttpClientResponse): Promise<any> => {
@@ -30,7 +30,7 @@ this.context.httpClient
 
 Similarly to the SPHttpClient you use for connecting to SharePoint APIs, the HttpClient offers you similar capabilities for performing the most common web requests. If necessary, you can use its options, to configure requests. For example, to specify request headers, you would use the following code:
 
-```ts
+```typescript
 this.context.httpClient
   .get('https://jsonplaceholder.typicode.com/todos/1', HttpClient.configurations.v1,
     {

docs/spfx/connect-to-sharepoint.md

@@ -14,7 +14,7 @@ In your SharePoint Framework solutions, you will likely want to interact with da
 
 SharePoint Framework offers the SPHttpClient that you can use to connect to SharePoint REST APIs. A ready-to-use instance of the SPHttpClient is available on the web part/extension context and you can use it to perform all kinds of web request. Following code snippet shows how you would use the SPHttpClient to retrieve the title of the current site:
 
-```ts
+```typescript
 this.context.spHttpClient
   .get(`${this.context.pageContext.web.absoluteUrl}/_api/web?$select=Title`, SPHttpClient.configurations.v1)
   .then((res: SPHttpClientResponse): Promise<{ Title: string; }> => {
@@ -27,7 +27,7 @@ this.context.spHttpClient
 
 The SPHttpClient offers basic functionality for performing the most common web requests. It allows you also, to configure your request by for example specifying request headers. For example, if you wanted to issue a web request without retrieving metadata, you'd use the following code:
 
-```ts
+```typescript
 this.context.spHttpClient
   .get(`${this.context.pageContext.web.absoluteUrl}/_api/web?$select=Title`,
     SPHttpClient.configurations.v1,
@@ -52,7 +52,7 @@ When using the SPHttpClient there are a few things that you should take into acc
 
 By default, the SPHttpClient uses OData v4 specification, which requires using `odata.metadata` instead of just `odata` to control the response metadata. If you use the `odata` directive in OData v4 mode, you will get an error, like: _The HTTP header ACCEPT is missing or its value is invalid._. It is  possible to set the SPHttpClient to OData v3.0 mode, by setting the `odata-version` request header to empty value:
 
-```ts
+```typescript
 this.context.spHttpClient
   .get(`${this.context.pageContext.web.absoluteUrl}/_api/web?$select=Title`,
     SPHttpClient.configurations.v1,
@@ -86,7 +86,7 @@ The SPHttpClient offers basic support for communicating with the SharePoint REST
 
 [PnPjs](https://pnp.github.io/pnpjs/) is an open-source JavaScript library for communicating with SharePoint and Office 365. It exposes a fluent API that allows you to easily consume SharePoint and Office 365 REST APIs in a type-safe way. To retrieve a the title of the current site using PnPjs, you would execute the following code:
 
-```ts
+```typescript
 sp.web
   .select('Title')
   .get<{Title: string;}>()

docs/spfx/dynamic-data.md

@@ -21,7 +21,7 @@ Dynamic data in the SharePoint Framework is based on the source-notification mod
 
 Every dynamic data source implements the `IDynamicDataCallables` interface. Following, is an example of a web part that displays a list of upcoming events. For each event, it includes some information such as its name, description, and ___location. The events web part exposes information about the selected event to other components on the page in two ways: the complete event information and the ___location address.
 
-```ts
+```typescript
 import {
   IDynamicDataPropertyDefinition,
   IDynamicDataCallables
@@ -157,7 +157,7 @@ In the example code, the web part displays upcoming events in a list. Each time,
 
 Web parts can consume data exposed by dynamic data sources present on the page. Following is the code of a web part showing on a map the ___location of the event selected in the events list web part showed previously.
 
-```ts
+```typescript
 import { DynamicProperty } from '@microsoft/sp-component-base';
 import {
   DynamicDataSharedDepth,
@@ -329,7 +329,7 @@ SharePoint Framework offers standard UI for connecting web parts to dynamic data
 
 Each web part property, for which the data can be retrieved from a dynamic data source, should be defined as `DynamicProperty<T>` where the `T` type denotes the type of data stored in the property, for example:
 
-```ts
+```typescript
 /**
  * Map web part properties
  */
@@ -349,7 +349,7 @@ In this example, the address is a string, but other types of data such as boolea
 
 For each dynamic property, you have to specify the type of data it holds. This is necessary, so that the instance of the web part added to a page can be properly serialized. For each dynamic web part property, in the `propertiesMetadata` getter, specify the `dynamicPropertyType` value:
 
-```ts
+```typescript
 protected get propertiesMetadata(): IWebPartPropertiesMetadata {
   return {
     // Specify the web part properties data type to allow the address
@@ -377,7 +377,7 @@ To allow users to connect web parts to dynamic data sources available on the pag
 
 In its simplest form, the UI could be defined as follows:
 
-```ts
+```typescript
 protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {
   return {
     pages: [
@@ -406,7 +406,7 @@ For each set of dynamic properties, add a new group using the `PropertyPaneDynam
 
 If your dynamic data field set consists of multiple dynamic properties, you can specify how the connection data is shared using the `sharedConfiguration.depth`  property:
 
-```ts
+```typescript
 groupFields: [
   PropertyPaneDynamicFieldSet({
     label: 'Address',
@@ -433,7 +433,7 @@ When building web parts, you can allow users to connect web parts to other compo
 
 To allow users to choose if they want to load data from a dynamic property or enter the value themselves in the web part properties, you can define the web part properties group as a `IPropertyPaneConditionalGroup` group.
 
-```ts
+```typescript
 protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {
   return {
     pages: [

docs/spfx/office-ui-fabric-integration.md

@@ -300,7 +300,7 @@ Solutions build with *no JavaScript framework* option.
 1. Add `@uifabric/styling` package to your `package.json`
 1. Make code changes similar to below code, to get the required icon into your code:
 
-```ts
+```typescript
   import { getIconClassName } from '@uifabric/styling';
 
   return `<i class="${getIconClassName('Mail')}" />`;
@@ -311,7 +311,7 @@ Solutions build with *React* option or by using *React* in general.
 1. Add `office-ui-fabric-react` package to your `package.json`, if not already added.
 2. Make code changes similar to below code, to get the required icon into your code:
 
-```ts
+```typescript
   import { Icon } from 'office-ui-fabric-react/lib/Icon';
 
   <Icon iconName='Mail' />

docs/spfx/subscribe-to-list-notifications.md

@@ -24,7 +24,7 @@ To subscribe to changes to files stored in a SharePoint Document Library, create
 
 Following, is an example of a list subscription for a Document Library located in the current site:
 
-```ts
+```typescript
 import { ListSubscriptionFactory, IListSubscription } from '@microsoft/sp-list-subscription';
 import { Guid } from '@microsoft/sp-core-library';
 
@@ -60,7 +60,7 @@ Depending on your solution, you might need to provide additional configuration w
 
 If you use SharePoint in a multi-geography tenancy, you need to provide the ___domain where the particular site collection lives in. You can do it, using the `___domain` property, for example:
 
-```ts
+```typescript
 this._listSubscriptionFactory.createSubscription({
   ___domain: this.properties.siteDomain,
   siteId: Guid.parse(this.properties.siteId),
@@ -78,7 +78,7 @@ In some cases, you might want to get notified when the component that you're bui
 
 The list subscription API, exposes two additional callbacks which you can implement to respond to the subscription status. The following code illustrates the case, where the component will be notified when the subscription has been established and when it was disconnected.
 
-```ts
+```typescript
 private createListSubscription(): void {
   this._listSubscriptionFactory.createSubscription({
     ___domain: this.properties.siteDomain,

docs/spfx/toolchain/implement-ci-cd-with-azure-devops.md

@@ -115,7 +115,7 @@ You also need to configure your project to leverage jest when typing commands. T
 
 To write your first unit test, create a new file `src/webparts/webPartName/tests/webPartName.spec.ts` and add the following content:
 
-```TS
+```typescript
 import 'jest'
 
 describe("webPartName", () => {

docs/spfx/use-aadhttpclient-enterpriseapi-multitenant.md

@@ -352,13 +352,13 @@ In the code editor, open the **src\webparts\orders\OrdersWebPart.ts** file.
 
 In the top section of the file, reference the **AadHttpClient** and **HttpClientResponse** classes, by adding the following code snippet:
 
-```ts
+```typescript
 import { AadHttpClient, HttpClientResponse } from '@microsoft/sp-http';
 ```
 
 To the **OrdersWebPart** class, add a new class variable named `ordersClient`:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 
@@ -368,7 +368,7 @@ export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartP
 
 Next, in the **OrdersWebPart** class, override the **onInit** method to create an instance of the AadHttpClient:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 
@@ -391,7 +391,7 @@ The URI passed into the `getClient()` method is the Application ID URI of the Az
 
 Finally, extend the **render** method to load and display orders retrieved from the enterprise API:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 

docs/spfx/use-aadhttpclient-enterpriseapi.md

@@ -290,13 +290,13 @@ In the code editor, open the **src\webparts\orders\OrdersWebPart.ts** file:
 
 In the top section of the file, reference the **AadHttpClient** and **HttpClientResponse** classes, by adding the following code snippet:
 
-```ts
+```typescript
 import { AadHttpClient, HttpClientResponse } from '@microsoft/sp-http';
 ```
 
 To the **OrdersWebPart** class, add a new class variable named `ordersClient`:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 
@@ -306,7 +306,7 @@ export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartP
 
 Next, in the **OrdersWebPart** class, override the **onInit** method to create an instance of the AadHttpClient:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 
@@ -329,7 +329,7 @@ The GUID passed as the second parameter of the **AadHttpClient** constructor, is
 
 Finally, extend the **render** method to load and display orders retrieved from the enterprise API:
 
-```ts
+```typescript
 export default class OrdersWebPart extends BaseClientSideWebPart<IOrdersWebPartProps> {
   private ordersClient: AadHttpClient;
 

docs/spfx/use-developer-dashboard.md

@@ -32,7 +32,7 @@ When building SharePoint Framework components, you can use the built-in logger t
 
 Following, is how you would log a verbose message to the SharePoint Framework developer dashboard:
 
-```ts
+```typescript
 // [...] shortened for brevity
 import { Log } from '@microsoft/sp-core-library';
 

docs/spfx/web-parts/basics/working-with-requestdigest.md

@@ -53,7 +53,7 @@ The benefit of using the DigestCache service over manually obtaining a valid req
 
 1. Import the **DigestCache** and **IDigestCache** types from the **\@microsoft/sp-http** package:
 
-    ```ts
+    ```typescript
     // ...
     import { IDigestCache, DigestCache } from '@microsoft/sp-http';
 
@@ -64,7 +64,7 @@ The benefit of using the DigestCache service over manually obtaining a valid req
 
 1. Whenever you need a valid request digest token, retrieve a reference to the DigestCache service, and call its **fetchDigest** method:
 
-    ```ts
+    ```typescript
     // ...
     import { IDigestCache, DigestCache } from '@microsoft/sp-http';