Document with code sample a production way of sharing the API client instance across the app + can this be the same as the Authentication context

[devraj]

The API Client is instantiated (both for autorest and otc) and it can keep track of authentication tokens and automatically add that to the header as required. Both clients generate wrappers for calling the API endpoints.

Using React context we could pass the API client (I need to critique this after the initial implementation, but on first thoughts it seems to be a legitimate option).

An reference implementation to be provided and this ticket needs to be revisited.

[devraj]

Study the sample Auth Context provider in React Router DOM documentation to make a judgement call.

[devraj]

A first cut implementation in the first project trialing labs proves to feel right:

import { createContext } from "react";  
import { AcaciaApiClient } from 'api/otc';

// Application level context
export interface AppContextInterface {
    apiClient: AcaciaApiClient;
}
  
export const AppContext = createContext<AppContextInterface | null>(null);