Fix JS typedoc links (#2067)

Author: ZhongpinWang

docs-js/features/connectivity/destination-cache-isolation.mdx

@@ -22,20 +22,20 @@ To reduce the number of calls to fetch destinations, the SAP Cloud SDK provides
 This guide explains how destinations are cached and shows options for destination cache configuration.
 The general destination lookup is described in [this guide](./destination.mdx).
 
-All options discussed in the following are part of the [`DestinationFetchOptions`](pathname:///api/v4/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html).
+All options discussed in the following are part of the [`DestinationFetchOptions`](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html).
 You use those options when:
 
 - executing requests through a generated client using `execute()`
-- executing generic HTTP requests using [`executeHttpRequest()`](pathname:///api/v4/functions/sap_cloud_sdk_http_client.executeHttpRequest.html)
-- retrieving destinations using [`getDestination()`](pathname:///api/v4/functions/sap_cloud_sdk_connectivity.getDestination.html)
-- retrieving all destinations using[`getAllDestinationsFromDestinationService()`](pathname:///api/v4/functions/sap_cloud_sdk_connectivity.getAllDestinationsFromDestinationService.html)
+- executing generic HTTP requests using [`executeHttpRequest()`](pathname:///api/v4/functions/sap-cloud-sdk_http_client.executeHttpRequest.html)
+- retrieving destinations using [`getDestination()`](pathname:///api/v4/functions/sap-cloud-sdk_connectivity.getDestination.html)
+- retrieving all destinations using[`getAllDestinationsFromDestinationService()`](pathname:///api/v4/functions/sap-cloud-sdk_connectivity.getAllDestinationsFromDestinationService.html)
 
 The following examples will use `execute()` for brevity, but could be replaced by all of the above.
 
 ## Destination Cache
 
 By default, destination caching is enabled.
-You can disable it by setting the [`useCache`](pathname:///api/v4/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html#useCache) option to `false`:
+You can disable it by setting the [`useCache`](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html#useCache) option to `false`:
 
 ```ts
 .execute({ destinationName: 'DESTINATION', jwt: 'JWT', useCache: false })
@@ -87,7 +87,7 @@ Assume you have a multi-tenant scenario, where you pass a JWT to obtain the dest
 The JWT contains a `user_id` but the authentication type of the destination is user-independent.
 The default isolation strategy for this case is `tenant-user`, although `tenant` would suffice.
 
-For such cases, you can manually enforce weaker isolation by passing the [`isolationStrategy`](pathname:///api/v4/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html#isolationStrategy) option:
+For such cases, you can manually enforce weaker isolation by passing the [`isolationStrategy`](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html#isolationStrategy) option:
 
 ```ts
 .execute({
@@ -107,7 +107,7 @@ An erroneous configuration can have severe consequences like privilege escalatio
 
 By default, destinations are cached in-memory.
 If you need more control over the destination cache, e.g. to use a persistent or distributed cache, you can create a custom destination cache.
-For this, implement the [`DestinationCacheInterface`](pathname:///api/v4/interfaces/sap_cloud_sdk_connectivity.DestinationCacheInterface.html):
+For this, implement the [`DestinationCacheInterface`](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.DestinationCacheInterface.html):
 
 ```ts
 export interface DestinationCacheInterface {
@@ -134,7 +134,7 @@ export interface DestinationCacheInterface {
 }
 ```
 
-Note that each item in the cache is represented using the [`CacheEntry<T>`](pathname:///api/v4/interfaces/sap_cloud_sdk_connectivity.CacheEntry.html) type, which defines two properties:
+Note that each item in the cache is represented using the [`CacheEntry<T>`](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.CacheEntry.html) type, which defines two properties:
 
 - `entry` - The item, i.e. destination, you want to cache.
 - `expires` - The expiration time of the entry in milliseconds.
@@ -167,7 +167,7 @@ const customCache = {
 };
 ```
 
-To use your custom cache, pass your implementation to the global [`setDestinationCache()`](pathname:///api/v4/functions/sap_cloud_sdk_connectivity.setDestinationCache.html) function before fetching destinations for the first time.
+To use your custom cache, pass your implementation to the global [`setDestinationCache()`](pathname:///api/v4/functions/sap-cloud-sdk_connectivity.setDestinationCache.html) function before fetching destinations for the first time.
 All subsequent calls to fetch destinations will use the custom cache.
 
 ```ts
@@ -180,7 +180,7 @@ setDestinationCache(customCache);
 
 ## Registered Destination Cache
 
-When [registering destinations](./destination.mdx#register-destination) using the [`registerDestination()`](pathname:///api/v4/functions/sap_cloud_sdk_connectivity.registerDestination.html) function, destinations are stored in a separate cache.
+When [registering destinations](./destination.mdx#register-destination) using the [`registerDestination()`](pathname:///api/v4/functions/sap-cloud-sdk_connectivity.registerDestination.html) function, destinations are stored in a separate cache.
 This cache is always enabled and behaves similarly to the destination cache discussed above.
 It uses the same JWT-dependent defaults for the [isolation strategy](#isolation-strategy) as the destination cache.
 To change the isolation strategy pass the `isolationStrategy` option to the function.

docs-js/features/connectivity/destination.mdx

@@ -33,7 +33,7 @@ Some reasons to separate destinations and the application are:
 - Different customers may want to configure different systems.
 - Multiple applications might want to access the same systems.
 
-Use [destinations](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.Destination.html) to execute [arbitrary requests](./generic-http-client.mdx), [OData requests](../odata/overview.mdx), and [OpenAPI requests](../openapi/overview.mdx).
+Use [destinations](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.Destination.html) to execute [arbitrary requests](./generic-http-client.mdx), [OData requests](../odata/overview.mdx), and [OpenAPI requests](../openapi/overview.mdx).
 The following examples use `req.execute()`, assuming req is an OData or OpenAPI request, to demonstrate options for the destination lookup.
 The same options apply to `executeHttpRequest()`.
 
@@ -64,7 +64,7 @@ If you want to cache destinations in production, use [`registerDestination()`](#
 :::
 
 You can provide destinations in the `destinations` environment variable.
-The value of the environment variable is expected to be a stringified JSON array, where the items adhere to the [Destination interface](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.Destination.html).
+The value of the environment variable is expected to be a stringified JSON array, where the items adhere to the [Destination interface](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.Destination.html).
 
 Example:
 
@@ -84,7 +84,7 @@ Note that this approach is **not suitable for multi-tenant scenarios**.
 #### Testing with Local Environment Variables
 
 The SAP Cloud SDK provides a `setTestDestination()` function to add a destination to the environment variable for the current process programmatically.
-It takes a [destination object](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.Destination.html), transforms it to a JSON object, and adds it to `process.env.destinations`.
+It takes a [destination object](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.Destination.html), transforms it to a JSON object, and adds it to `process.env.destinations`.
 
 ```ts
 import { setTestDestination } from '@sap-cloud-sdk/test-util';
@@ -280,7 +280,7 @@ Note, that if your `serviceBindingTransformFn()` function does not provide a nam
 
 More advanced examples with service token fetching can be found in [service-binding-to-destination.ts](https://github.com/SAP/cloud-sdk-js/blob/main/packages/connectivity/src/scp-cf/destination/service-binding-to-destination.ts).
 
-If you want to skip the destination lookup and consider only the service bindings, call the [getDestinationFromServiceBinding()](pathname:///api/v3/functions/sap_cloud_sdk_connectivity.getDestinationFromServiceBinding.html) function with the service name and options.
+If you want to skip the destination lookup and consider only the service bindings, call the [getDestinationFromServiceBinding()](pathname:///api/v4/functions/sap-cloud-sdk_connectivity.getDestinationFromServiceBinding.html) function with the service name and options.
 
 ```ts
 const destination = getDestinationFromServiceBinding({

docs-js/features/connectivity/generic-http-client.mdx

@@ -53,7 +53,7 @@ The generic HTTP client is based on the open source [axios HTTP client](https://
 
 ## `executeHttpRequest`
 
-The most basic way to use the SAP Cloud SDK HTTP client is the function [executeHttpRequest](pathname:///api/v3/functions/sap_cloud_sdk_http_client.executeHttpRequest.html).
+The most basic way to use the SAP Cloud SDK HTTP client is the function [executeHttpRequest](pathname:///api/v4/functions/sap-cloud-sdk_http_client.executeHttpRequest.html).
 
 ```ts
 executeHttpRequest(destination, requestConfig, httpRequestOptions): Promise<HttpResponse>;
@@ -62,8 +62,8 @@ executeHttpRequest(destination, requestConfig, httpRequestOptions): Promise<Http
 It takes the following parameters:
 
 - The `destination` argument is of type `DestinationOrFetchOptions`
-  - This can either be a [destination object](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.Destination.html) which was already fetched or an [object containing a destination name and an optional JWT](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html)
-- The `requestConfig` argument is of type [HttpRequestConfig](pathname:///api/v3/types/sap_cloud_sdk_http_client.HttpRequestConfig.html).
+  - This can either be a [destination object](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.Destination.html) which was already fetched or an [object containing a destination name and an optional JWT](pathname:///api/v4/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html)
+- The `requestConfig` argument is of type [HttpRequestConfig](pathname:///api/v4/types/sap-cloud-sdk_http_client.HttpRequestConfig.html).
   - This parameter is optional
   - The default value is a `GET` request
 - The `httpRequestOptions` argument is of type `HttpRequestOptions`
@@ -98,7 +98,7 @@ For keys that exist for both objects, the `requestConfig` takes precedence.
 
 :::
 
-The `executeHttpRequest()` function returns a promise of type [HttpResponse](pathname:///api/v3/interfaces/sap_cloud_sdk_http_client.HttpResponse.html).
+The `executeHttpRequest()` function returns a promise of type [HttpResponse](pathname:///api/v4/interfaces/sap-cloud-sdk_http_client.HttpResponse.html).
 
 ### Parameter Encoding
 
@@ -177,7 +177,7 @@ It is not available for `GET` requests.
 :::
 
 Fetching the CSRF token can be enabled or disabled via the `httpRequestOptions.fetchCsrfToken` parameter of `executeHttpRequest()` function.
-See its [API documentation](pathname:///api/v3/interfaces/sap_cloud_sdk_http_client.HttpRequestOptions.html) for details.
+See its [API documentation](pathname:///api/v4/interfaces/sap-cloud-sdk_http_client.HttpRequestOptions.html) for details.
 
 For example, to avoid CSRF token fetching when doing a `PUT`, `POST`, `DELETE`, or `PATCH` request, disable it like in this example:
 

docs-js/features/odata/execute-odata-request.mdx

@@ -167,10 +167,10 @@ The following table describes how types are mapped by default:
 | `Edm.DateTimeOffset` | `moment.Moment`                                                              |                                                       |
 | `Edm.Binary`         | `string`                                                                     |                                                       |
 | `Edm.DateTime`       | `moment.Moment`                                                              | OData v2 only, precision limited to milliseconds      |
-| `Edm.Time`           | [`Time`](pathname:///api/v3/interfaces/sap_cloud_sdk_odata_common.Time.html) | OData v2 only, does not consider time zones           |
+| `Edm.Time`           | [`Time`](pathname:///api/v4/interfaces/sap-cloud-sdk_odata_common.Time.html) | OData v2 only, does not consider time zones           |
 | `Edm.Date`           | `moment.Moment`                                                              | OData v4 only                                         |
 | `Edm.Duration`       | `moment.Duration`                                                            | OData v4 only                                         |
-| `Edm.TimeOfDay`      | [`Time`](pathname:///api/v3/interfaces/sap_cloud_sdk_odata_common.Time.html) | OData v4 only, does not consider time-zones           |
+| `Edm.TimeOfDay`      | [`Time`](pathname:///api/v4/interfaces/sap-cloud-sdk_odata_common.Time.html) | OData v4 only, does not consider time-zones           |
 | Any other type       | `any`                                                                        |                                                       |
 
 If you require the raw OData response, you can look into [getting the raw response and the original request](#getting-the-raw-response-and-the-original-request).

docs-js/tutorials/multi-tenant-application.mdx

@@ -537,7 +537,7 @@ You are on tenant: a89ea924-d9c2-4gaf-84fb-3ffcff7891011. The destination descri
 ```
 
 The destination of the subscriber account is used at runtime, because the call in the `service-endpoint.ts` uses the selection strategy `subscriberFirst`.
-You can change this by using [different selection strategies](pathname:///api/v3/variables/sap_cloud_sdk_connectivity.DestinationSelectionStrategies).
+You can change this by using [different selection strategies](pathname:///api/v4/variables/sap-cloud-sdk_connectivity.DestinationSelectionStrategies).
 This enables consumers to maintain their custom destination used within a multi-tenant application.
 The destination from the provider account could be seen as a fallback.
 

docs-js_versioned_docs/version-v3/features/connectivity/destination-cache-isolation.mdx

@@ -22,19 +22,19 @@ To reduce the number of calls to fetch destinations, the SAP Cloud SDK provides
 This guide explains how destinations are cached and shows options for destination cache configuration.
 The general destination lookup is described in [this guide](./destination.mdx).
 
-All options discussed in the following are part of the [`DestinationFetchOptions`](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html).
+All options discussed in the following are part of the [`DestinationFetchOptions`](pathname:///api/v3/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html).
 You use those options when:
 
 - executing requests through a generated client using `execute()`
-- executing generic HTTP requests using [`executeHttpRequest()`](pathname:///api/v3/functions/sap_cloud_sdk_http_client.executeHttpRequest.html)
-- retrieving destinations using [`getDestination()`](pathname:///api/v3/functions/sap_cloud_sdk_connectivity.getDestination.html)
+- executing generic HTTP requests using [`executeHttpRequest()`](pathname:///api/v3/functions/sap-cloud-sdk_http_client.executeHttpRequest.html)
+- retrieving destinations using [`getDestination()`](pathname:///api/v3/functions/sap-cloud-sdk_connectivity.getDestination.html)
 
 The following examples will use `execute()` for brevity, but could be replaced by all of the above.
 
 ## Destination Cache
 
 By default, destination caching is disabled.
-Enable it by setting the [`useCache`](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html#useCache) option to `true`:
+Enable it by setting the [`useCache`](pathname:///api/v3/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html#useCache) option to `true`:
 
 ```ts
 .execute({ destinationName: 'DESTINATION', jwt: 'JWT', useCache: true })
@@ -86,7 +86,7 @@ Assume you have a multi-tenant scenario, where you pass a JWT to obtain the dest
 The JWT contains a `user_id` but the authentication type of the destination is user-independent.
 The default isolation strategy for this case is `tenant-user`, although `tenant` would suffice.
 
-For such cases, you can manually enforce weaker isolation by passing the [`isolationStrategy`](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.DestinationFetchOptions.html#isolationStrategy) option:
+For such cases, you can manually enforce weaker isolation by passing the [`isolationStrategy`](pathname:///api/v3/interfaces/sap-cloud-sdk_connectivity.DestinationFetchOptions.html#isolationStrategy) option:
 
 ```ts
 .execute({
@@ -106,7 +106,7 @@ An erroneous configuration can have severe consequences like privilege escalatio
 
 When caching is enabled, destinations are cached in-memory.
 If you need more control over the destination cache, e.g. to use a persistent or distributed cache, you can create a custom destination cache.
-For this, implement the [`DestinationCacheInterface`](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.DestinationCacheInterface.html):
+For this, implement the [`DestinationCacheInterface`](pathname:///api/v3/interfaces/sap-cloud-sdk_connectivity.DestinationCacheInterface.html):
 
 ```ts
 export interface DestinationCacheInterface {
@@ -133,7 +133,7 @@ export interface DestinationCacheInterface {
 }
 ```
 
-Note that each item in the cache is represented using the [`CacheEntry<T>`](pathname:///api/v3/interfaces/sap_cloud_sdk_connectivity.CacheEntry.html) type, which defines two properties:
+Note that each item in the cache is represented using the [`CacheEntry<T>`](pathname:///api/v3/interfaces/sap-cloud-sdk_connectivity.CacheEntry.html) type, which defines two properties:
 
 - `entry` - The item, i.e. destination, you want to cache.
 - `expires` - The expiration time of the entry in milliseconds.
@@ -166,7 +166,7 @@ const customCache = {
 };
 ```
 
-To use your custom cache, pass your implementation to the global [`setDestinationCache()`](pathname:///api/v3/functions/sap_cloud_sdk_connectivity.setDestinationCache.html) function before fetching destinations for the first time.
+To use your custom cache, pass your implementation to the global [`setDestinationCache()`](pathname:///api/v3/functions/sap-cloud-sdk_connectivity.setDestinationCache.html) function before fetching destinations for the first time.
 All subsequent calls to fetch destinations will use the custom cache.
 
 ```ts
@@ -179,7 +179,7 @@ setDestinationCache(customCache);
 
 ## Registered Destination Cache
 
-When [registering destinations](./destination.mdx#register-destination) using the [`registerDestination()`](pathname:///api/v3/functions/sap_cloud_sdk_connectivity.registerDestination.html) function, destinations are stored in a separate cache.
+When [registering destinations](./destination.mdx#register-destination) using the [`registerDestination()`](pathname:///api/v3/functions/sap-cloud-sdk_connectivity.registerDestination.html) function, destinations are stored in a separate cache.
 This cache is always enabled and behaves similarly to the destination cache discussed above.
 It uses the same JWT-dependent defaults for the [isolation strategy](#isolation-strategy) as the destination cache.
 To change the isolation strategy pass the `isolationStrategy` option to the function.