Skip to content

Commit 064b1f3

Browse files
committed
Remove table to describe operation
Signed-off-by: Ricardo Zanini <[email protected]>
1 parent 2b26931 commit 064b1f3

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

specification.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1088,13 +1088,12 @@ Note that the [Function Definition](#Function-Definition)'s `operation` property
10881088
* The HTTP method used by the HTTP invocation. Can be any [valid HTTP method](https://www.rfc-editor.org/rfc/rfc9110.html#name-method-definitions) such as `GET`, `POST`, `PUT`, etc.
10891089
* The endpoint **location path** or the service full URL. Runtimes implementations are **discouraged** to expect the full URL in this field since this is a matter of infrastructure configuration.
10901090

1091-
The table below lists how to describe the HTTP parameters in the `operation` attribute:
1091+
The list below describes the HTTP function parameters in the `operation` attribute:
10921092

1093-
| Parameter | Description | Example |
1094-
| --- | --- | --- |
1095-
| Path | Path parameters must be enclosed with braces (`{}`) as defined by [URI Templates](https://www.rfc-editor.org/rfc/rfc6570.html). The parameter name can be later referenced by the workflow states. | `/user/{id}` |
1096-
| Query | [Query parameters](https://www.rfc-editor.org/rfc/rfc9110.html#section-4.2.2) must be enclosed with braces (`{}`) as defined by [URI Templates](https://www.rfc-editor.org/rfc/rfc6570.html). The parameter name can be later referenced by the workflow states. | `/user?status={status}` |
1093+
* Path parameters must be enclosed with braces (`{}`) as defined by [URI Templates](https://www.rfc-editor.org/rfc/rfc6570.html). The parameter name can be later referenced by the workflow states. For example: `/user/{id}`
1094+
* [Query parameters](https://www.rfc-editor.org/rfc/rfc9110.html#section-4.2.2) must be enclosed with braces (`{}`) as defined by [URI Templates](https://www.rfc-editor.org/rfc/rfc6570.html). The parameter name can be later referenced by the workflow states. For example: `/user?status={status}`.
10971095

1096+
<!-- TODO: refine how we are going to describe http headers parameters -->
10981097
Additional HTTP header fields can be passed via the `metadata` function definition. For example:
10991098

11001099
```json

0 commit comments

Comments
 (0)