Skip to content

Commit b6f81ea

Browse files
committed
Fixed anchors for Links/Link
1 parent c3cea4e commit b6f81ea

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

versions/3.0.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1998,7 +1998,7 @@ For computing links, and providing instructions to execute them, [variable subst
19981998
##### Patterned Fields
19991999
Field Pattern | Type | Description
20002000
---|:---:|---
2001-
<a name="linkName"></a> {name} | [Link Object](#linkObject) \| [Reference Object](#referenceObject) | A short name for the link, following the naming constraints of the names for [Component Objects](#componentsObject). The link SHALL reference a single Link Object, or a JSON Reference to a single link object.
2001+
<a name="linksName"></a> {name} | [Link Object](#linkObject) \| [Reference Object](#referenceObject) | A short name for the link, following the naming constraints of the names for [Component Objects](#componentsObject). The link SHALL reference a single Link Object, or a JSON Reference to a single link object.
20022002

20032003
#### <a name="linkObject"></a>Link Object
20042004
The `Link Object` is responsible for defining a possible operation based on a single response.
@@ -2007,12 +2007,12 @@ The `Link Object` is responsible for defining a possible operation based on a si
20072007

20082008
Field Name | Type | Description
20092009
---|:---:|---
2010-
operationRef | `string` | a relative or absolute reference to an OAS operation. This field is mutually exclusive with the `operationId` field, and must point to the fragment of a valid OAS definition
2011-
operationId | `string` | the name of an _existing_, resolvable OAS operation, as defined with a unique `operationId`. This field is mutually exclusive with the `operationRef` field. Relative `operationRef` values MAY be used to locate an existing [Operation Object](#operationObject) in the OAS.
2012-
parameters | [Link Parameters Object](#linkParametersObject) | an object representing parameters to pass to an operation as specified with `operationId` or identified via `operationRef`.
2013-
headers | [Headers Object](#headersObject) | an object representing headers to pass to the linked resource. Where conflicts occur between these headers, and those defined in the related operation, these headers override.
2014-
description | `string` | a description of the link, supports [CommonMark syntax](http://spec.commonmark.org/).
2015-
server | [Server Object](#serverObject) | a server object to be used by the target operation
2010+
<a name="linkOperationRef"></a>operationRef | `string` | a relative or absolute reference to an OAS operation. This field is mutually exclusive with the `operationId` field, and must point to the fragment of a valid OAS definition.
2011+
<a name="linkOperationId"></a>operationId | `string` | the name of an _existing_, resolvable OAS operation, as defined with a unique `operationId`. This field is mutually exclusive with the `operationRef` field. Relative `operationRef` values MAY be used to locate an existing [Operation Object](#operationObject) in the OAS.
2012+
<a name="linkParameters"></a>parameters | [Link Parameters Object](#linkParametersObject) | an object representing parameters to pass to an operation as specified with `operationId` or identified via `operationRef`.
2013+
<a name="linkHeaders"></a>headers | [Headers Object](#headersObject) | an object representing headers to pass to the linked resource. Where conflicts occur between these headers, and those defined in the related operation, these headers override.
2014+
<a name="linkDescription"></a>description | `string` | a description of the link, supports [CommonMark syntax](http://spec.commonmark.org/).
2015+
<a name="linkServer"></a>server | [Server Object](#serverObject) | a server object to be used by the target operation.
20162016

20172017
This object can be extended with [Specification Extensions](#specificationExtensions).
20182018

0 commit comments

Comments
 (0)