docs: add {@link} and @see tags to JSDoc comments (#1490)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
64fb21d7a7
commit
efed431843
2 changed files with 27 additions and 8 deletions
|
|
@ -654,7 +654,8 @@ export function extractResourceMetadataUrl(res: Response): URL | undefined {
|
|||
}
|
||||
|
||||
/**
|
||||
* Looks up RFC 9728 OAuth 2.0 Protected Resource Metadata.
|
||||
* Looks up {@link https://datatracker.ietf.org/doc/html/rfc9728 | RFC 9728}
|
||||
* OAuth 2.0 Protected Resource Metadata.
|
||||
*
|
||||
* If the server returns a 404 for the well-known endpoint, this function will
|
||||
* return `undefined`. Any other errors will be thrown as exceptions.
|
||||
|
|
@ -872,8 +873,11 @@ export function buildDiscoveryUrls(authorizationServerUrl: string | URL): { url:
|
|||
}
|
||||
|
||||
/**
|
||||
* Discovers authorization server metadata with support for RFC 8414 OAuth 2.0 Authorization Server Metadata
|
||||
* and OpenID Connect Discovery 1.0 specifications.
|
||||
* Discovers authorization server metadata with support for
|
||||
* {@link https://datatracker.ietf.org/doc/html/rfc8414 | RFC 8414} OAuth 2.0
|
||||
* Authorization Server Metadata and
|
||||
* {@link https://openid.net/specs/openid-connect-discovery-1_0.html | OpenID Connect Discovery 1.0}
|
||||
* specifications.
|
||||
*
|
||||
* This function implements a fallback strategy for authorization server discovery:
|
||||
* 1. Attempts RFC 8414 OAuth metadata discovery first
|
||||
|
|
@ -1269,7 +1273,8 @@ export async function fetchToken(
|
|||
}
|
||||
|
||||
/**
|
||||
* Performs OAuth 2.0 Dynamic Client Registration according to RFC 7591.
|
||||
* Performs OAuth 2.0 Dynamic Client Registration according to
|
||||
* {@link https://datatracker.ietf.org/doc/html/rfc7591 | RFC 7591}.
|
||||
*/
|
||||
export async function registerClient(
|
||||
authorizationServerUrl: string | URL,
|
||||
|
|
|
|||
|
|
@ -223,7 +223,8 @@ export interface PrivateKeyJwtProviderOptions {
|
|||
* OAuth provider for client_credentials grant with private_key_jwt authentication.
|
||||
*
|
||||
* This provider is designed for machine-to-machine authentication where
|
||||
* the client authenticates using a signed JWT assertion (RFC 7523 Section 2.2).
|
||||
* the client authenticates using a signed JWT assertion
|
||||
* ({@link https://datatracker.ietf.org/doc/html/rfc7523#section-2.2 | RFC 7523 Section 2.2}).
|
||||
*
|
||||
* @example
|
||||
* ```typescript
|
||||
|
|
|
|||
Loading…
Reference in a new issue