Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: move Parameter Object spec extensions under the fields definition #83

Merged
merged 1 commit into from
Nov 22, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
docs: move Parameter Object spec extensions under the fields definition
char0n committed Nov 22, 2023
commit f8aad55b3c2fddc172b71cb2237fcbbbc5260ee2
4 changes: 2 additions & 2 deletions versions/1.0.0.md
Original file line number Diff line number Diff line change
@@ -413,6 +413,8 @@ Field Name | Type | Description
<a name="parameterTarget"></a> target | {JSON Pointer} | A [JSON Pointer](https://tools.ietf.org/html/rfc6901) expression identifying locations to inject the value. Can be useful for targeting specific request body part.
<a name="parameterValue"></a> value | Any \| {expression} | **REQUIRED**. The value to pass in the parameter. The value can be a constant or an [expression](#runtime-expressions) to be evaluated and passed to the referenced operation or workflow.

This object MAY be extended with [Specification Extensions](#specification-extensions).

##### Parameter Object Example
**Query Example**

@@ -451,8 +453,6 @@ Field Name | Type | Description
value: $inputs.scope
```

This object MAY be extended with [Specification Extensions](#specification-extensions).

#### Success Action Object

A single success action which describes an action to take upon success of a workflow step. There are two possible values for the `type` field.