@things-factory/integration-base 6.2.44 → 6.2.48
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist-server/engine/connector/operato-connector.js +10 -7
- package/dist-server/engine/connector/operato-connector.js.map +1 -1
- package/dist-server/engine/types.js.map +1 -1
- package/dist-server/service/scenario-instance/scenario-instance-mutation.js +15 -9
- package/dist-server/service/scenario-instance/scenario-instance-mutation.js.map +1 -1
- package/dist-server/service/scenario-instance/scenario-instance-type.js +2 -1
- package/dist-server/service/scenario-instance/scenario-instance-type.js.map +1 -1
- package/dist-server/tsconfig.tsbuildinfo +1 -1
- package/helps/integration/connector/graphql-connector.ja.md +23 -0
- package/helps/integration/connector/graphql-connector.ko.md +23 -0
- package/helps/integration/connector/graphql-connector.ms.md +23 -0
- package/helps/integration/connector/graphql-connector.zh.md +23 -0
- package/helps/integration/connector/mqtt-connector.ja.md +17 -0
- package/helps/integration/connector/mqtt-connector.ko.md +17 -0
- package/helps/integration/connector/mqtt-connector.ms.md +17 -0
- package/helps/integration/connector/mqtt-connector.zh.md +17 -0
- package/helps/integration/connector/mssql-connector.ja.md +38 -0
- package/helps/integration/connector/mssql-connector.ko.md +38 -0
- package/helps/integration/connector/mssql-connector.ms.md +38 -0
- package/helps/integration/connector/mssql-connector.zh.md +38 -0
- package/helps/integration/connector/postgresql-connector.ja.md +34 -0
- package/helps/integration/connector/postgresql-connector.ko.md +34 -0
- package/helps/integration/connector/postgresql-connector.ms.md +34 -0
- package/helps/integration/connector/postgresql-connector.zh.md +34 -0
- package/helps/integration/connector/sqlite-connector.ja.md +17 -0
- package/helps/integration/connector/sqlite-connector.ko.md +17 -0
- package/helps/integration/connector/sqlite-connector.ms.md +17 -0
- package/helps/integration/connector/sqlite-connector.zh.md +17 -0
- package/helps/integration/task/book-up-scenario.ja.md +27 -0
- package/helps/integration/task/book-up-scenario.ko.md +27 -0
- package/helps/integration/task/book-up-scenario.md +21 -21
- package/helps/integration/task/book-up-scenario.ms.md +27 -0
- package/helps/integration/task/book-up-scenario.zh.md +27 -0
- package/helps/integration/task/csv-readline.ja.md +10 -0
- package/helps/integration/task/csv-readline.ko.md +10 -0
- package/helps/integration/task/csv-readline.md +5 -6
- package/helps/integration/task/csv-readline.ms.md +9 -0
- package/helps/integration/task/csv-readline.zh.md +9 -0
- package/helps/integration/task/data-mapper.ja.md +14 -0
- package/helps/integration/task/data-mapper.ko.md +14 -0
- package/helps/integration/task/data-mapper.md +11 -11
- package/helps/integration/task/data-mapper.ms.md +14 -0
- package/helps/integration/task/data-mapper.zh.md +14 -0
- package/helps/integration/task/database-query.ja.md +1 -1
- package/helps/integration/task/database-query.ko.md +1 -1
- package/helps/integration/task/database-query.md +1 -1
- package/helps/integration/task/database-query.ms.md +1 -1
- package/helps/integration/task/database-query.zh.md +1 -1
- package/helps/integration/task/empty-check.ja.md +10 -0
- package/helps/integration/task/empty-check.ko.md +10 -0
- package/helps/integration/task/empty-check.md +7 -7
- package/helps/integration/task/empty-check.ms.md +10 -0
- package/helps/integration/task/empty-check.zh.md +10 -0
- package/helps/integration/task/end.ja.md +7 -0
- package/helps/integration/task/end.ko.md +3 -0
- package/helps/integration/task/end.md +6 -2
- package/helps/integration/task/end.ms.md +7 -0
- package/helps/integration/task/end.zh.md +7 -0
- package/helps/integration/task/floating-point.ja.md +34 -0
- package/helps/integration/task/floating-point.ko.md +34 -0
- package/helps/integration/task/floating-point.md +1 -1
- package/helps/integration/task/floating-point.ms.md +34 -0
- package/helps/integration/task/floating-point.zh.md +34 -0
- package/helps/integration/task/goto.ja.md +8 -0
- package/helps/integration/task/goto.ko.md +8 -0
- package/helps/integration/task/goto.md +4 -4
- package/helps/integration/task/goto.ms.md +8 -0
- package/helps/integration/task/goto.zh.md +8 -0
- package/helps/integration/task/graphql-mutate.ja.md +1 -1
- package/helps/integration/task/graphql-mutate.ko.md +1 -1
- package/helps/integration/task/graphql-mutate.md +1 -1
- package/helps/integration/task/graphql-mutate.ms.md +1 -1
- package/helps/integration/task/graphql-mutate.zh.md +1 -1
- package/helps/integration/task/graphql-query.ja.md +1 -1
- package/helps/integration/task/graphql-query.ko.md +1 -1
- package/helps/integration/task/graphql-query.md +1 -1
- package/helps/integration/task/graphql-query.ms.md +1 -1
- package/helps/integration/task/graphql-query.zh.md +1 -1
- package/helps/integration/task/headless-scrap.ja.md +13 -0
- package/helps/integration/task/headless-scrap.ko.md +13 -0
- package/helps/integration/task/headless-scrap.md +10 -10
- package/helps/integration/task/headless-scrap.ms.md +13 -0
- package/helps/integration/task/headless-scrap.zh.md +13 -0
- package/helps/integration/task/http-get.ja.md +1 -1
- package/helps/integration/task/http-get.ko.md +1 -1
- package/helps/integration/task/http-get.md +1 -1
- package/helps/integration/task/http-get.ms.md +1 -1
- package/helps/integration/task/http-get.zh.md +1 -1
- package/helps/integration/task/http-post.ja.md +1 -1
- package/helps/integration/task/http-post.ko.md +1 -1
- package/helps/integration/task/http-post.md +1 -1
- package/helps/integration/task/http-post.ms.md +1 -1
- package/helps/integration/task/http-post.zh.md +1 -1
- package/helps/integration/task/local-graphql-mutate.ja.md +43 -0
- package/helps/integration/task/local-graphql-mutate.ko.md +44 -0
- package/helps/integration/task/local-graphql-mutate.md +10 -14
- package/helps/integration/task/local-graphql-mutate.ms.md +40 -0
- package/helps/integration/task/local-graphql-mutate.zh.md +40 -0
- package/helps/integration/task/local-graphql-query.ja.md +42 -0
- package/helps/integration/task/local-graphql-query.ko.md +44 -0
- package/helps/integration/task/local-graphql-query.md +10 -14
- package/helps/integration/task/local-graphql-query.ms.md +41 -0
- package/helps/integration/task/local-graphql-query.zh.md +40 -0
- package/helps/integration/task/log.ja.md +1 -1
- package/helps/integration/task/log.ko.md +1 -1
- package/helps/integration/task/log.md +1 -1
- package/helps/integration/task/log.ms.md +1 -1
- package/helps/integration/task/log.zh.md +1 -1
- package/helps/integration/task/mqtt-publish.ja.md +10 -0
- package/helps/integration/task/mqtt-publish.ko.md +10 -0
- package/helps/integration/task/mqtt-publish.md +7 -7
- package/helps/integration/task/mqtt-publish.ms.md +10 -0
- package/helps/integration/task/mqtt-publish.zh.md +10 -0
- package/helps/integration/task/mqtt-subscribe.ja.md +15 -0
- package/helps/integration/task/mqtt-subscribe.ko.md +15 -0
- package/helps/integration/task/mqtt-subscribe.md +12 -12
- package/helps/integration/task/mqtt-subscribe.ms.md +15 -0
- package/helps/integration/task/mqtt-subscribe.zh.md +15 -0
- package/helps/integration/task/oracle-procedure.ja.md +1 -1
- package/helps/integration/task/oracle-procedure.ko.md +1 -1
- package/helps/integration/task/oracle-procedure.md +1 -1
- package/helps/integration/task/oracle-procedure.ms.md +1 -1
- package/helps/integration/task/oracle-procedure.zh.md +1 -1
- package/helps/integration/task/pick-pending-scenario.ja.md +13 -0
- package/helps/integration/task/pick-pending-scenario.ko.md +13 -0
- package/helps/integration/task/pick-pending-scenario.md +10 -10
- package/helps/integration/task/pick-pending-scenario.ms.md +13 -0
- package/helps/integration/task/pick-pending-scenario.zh.md +13 -0
- package/helps/integration/task/publish.ja.md +16 -0
- package/helps/integration/task/publish.ko.md +16 -0
- package/helps/integration/task/publish.md +10 -10
- package/helps/integration/task/publish.ms.md +16 -0
- package/helps/integration/task/publish.zh.md +16 -0
- package/helps/integration/task/random.ja.md +13 -0
- package/helps/integration/task/random.ko.md +13 -0
- package/helps/integration/task/random.md +9 -9
- package/helps/integration/task/random.ms.md +13 -0
- package/helps/integration/task/random.zh.md +13 -0
- package/helps/integration/task/script.ja.md +1 -1
- package/helps/integration/task/script.ko.md +1 -1
- package/helps/integration/task/script.md +1 -1
- package/helps/integration/task/script.ms.md +1 -1
- package/helps/integration/task/script.zh.md +1 -1
- package/helps/integration/task/set-domain.ja.md +25 -0
- package/helps/integration/task/set-domain.ko.md +25 -0
- package/helps/integration/task/set-domain.md +12 -12
- package/helps/integration/task/set-domain.ms.md +25 -0
- package/helps/integration/task/set-domain.zh.md +25 -0
- package/helps/integration/task/sleep.ja.md +8 -0
- package/helps/integration/task/sleep.ko.md +8 -0
- package/helps/integration/task/sleep.md +5 -5
- package/helps/integration/task/sleep.ms.md +8 -0
- package/helps/integration/task/sleep.zh.md +8 -0
- package/helps/integration/task/state-read.ja.md +1 -1
- package/helps/integration/task/state-read.ms.md +1 -1
- package/helps/integration/task/state-read.zh.md +1 -1
- package/helps/integration/task/state-write.ja.md +1 -1
- package/helps/integration/task/state-write.ms.md +1 -1
- package/helps/integration/task/state-write.zh.md +1 -1
- package/helps/integration/task/throw.ja.md +12 -0
- package/helps/integration/task/throw.ko.md +12 -0
- package/helps/integration/task/throw.md +10 -10
- package/helps/integration/task/throw.ms.md +12 -0
- package/helps/integration/task/throw.zh.md +12 -0
- package/helps/integration/task/variables.ja.md +37 -0
- package/helps/integration/task/variables.ko.md +37 -0
- package/helps/integration/task/variables.md +11 -11
- package/helps/integration/task/variables.ms.md +37 -0
- package/helps/integration/task/variables.zh.md +37 -0
- package/package.json +7 -7
- package/server/engine/connector/operato-connector.ts +23 -5
- package/server/engine/types.ts +1 -0
- package/server/service/scenario-instance/scenario-instance-mutation.ts +28 -9
- package/server/service/scenario-instance/scenario-instance-type.ts +2 -1
- /package/helps/integration/connector/{operato-connector.kr.md → operato-connector.ko.md} +0 -0
@@ -0,0 +1,13 @@
|
|
1
|
+
# headless-scrap
|
2
|
+
|
3
|
+
与えられたパスのウェブページをヘッドレスクロムで読み取った後、指定されたセレクタの値をスクラップし、それに対応する属性値として設定するタスクです。
|
4
|
+
|
5
|
+
## パラメータ
|
6
|
+
|
7
|
+
- パス (path)
|
8
|
+
- ヘッドレスクロムで読み取るウェブページのアドレス
|
9
|
+
- ヘッダー (headers)
|
10
|
+
- ウェブページを正常に取得するために提供する必要があるHTTPヘッダを設定します。
|
11
|
+
- 主に認証(Authentication)などの情報を含みます。
|
12
|
+
- セレクタ (selector)
|
13
|
+
- ウェブページから特定のコンテンツ値を取得するために対象をセレクタで指定します。
|
@@ -0,0 +1,13 @@
|
|
1
|
+
# headless-scrap
|
2
|
+
|
3
|
+
주어진 패스 주소의 웹페이지를 헤드리스크롬에서 읽은 후 주어진 셀렉터들의 값을 스크랩하여 해당하는 속성값으로 설정한다.
|
4
|
+
|
5
|
+
## parameters
|
6
|
+
|
7
|
+
- 패스 (path)
|
8
|
+
- 헤드리스크롬에서 읽을 웹페이지의 주소
|
9
|
+
- 헤더 (headers)
|
10
|
+
- 웹페이지를 정상적으로 가져오기위해 주어져야하는 http header들을 설정한다.
|
11
|
+
- 주로 Authentication 등의 정보를 제공한다.
|
12
|
+
- 셀렉터 (selector)
|
13
|
+
- 웹페이지안에서 특정 컨텐츠 값을 가져오기 위해 대상을 Selector로 지정한다.
|
@@ -1,13 +1,13 @@
|
|
1
|
-
# headless-scrap
|
1
|
+
# headless-scrap
|
2
2
|
|
3
|
-
|
3
|
+
This is a task that reads a web page at the given path address using headless Chrome, and then scrapes the values of the given selectors, setting them as corresponding attribute values.
|
4
4
|
|
5
|
-
##
|
5
|
+
## Parameters
|
6
6
|
|
7
|
-
-
|
8
|
-
-
|
9
|
-
-
|
10
|
-
-
|
11
|
-
-
|
12
|
-
-
|
13
|
-
-
|
7
|
+
- Path (path)
|
8
|
+
- The address of the web page to be read by headless Chrome.
|
9
|
+
- Headers (headers)
|
10
|
+
- Set the HTTP headers that need to be provided to fetch the web page successfully.
|
11
|
+
- Typically provides information like Authentication.
|
12
|
+
- Selector (selector)
|
13
|
+
- Specify the target as a selector to retrieve specific content values from the web page.
|
@@ -0,0 +1,13 @@
|
|
1
|
+
# headless-scrap
|
2
|
+
|
3
|
+
Ini adalah tugasan yang membaca laman web pada alamat path yang diberikan menggunakan Chrome tanpa tajuk, dan kemudian menggeret nilai-nilai selector yang diberikan, menetapkannya sebagai nilai atribut yang sepadan.
|
4
|
+
|
5
|
+
## Parameter
|
6
|
+
|
7
|
+
- Path (path)
|
8
|
+
- Alamat laman web yang akan dibaca oleh Chrome tanpa tajuk.
|
9
|
+
- Headers (headers)
|
10
|
+
- Tetapkan header HTTP yang perlu disediakan untuk mengambil laman web dengan berjaya.
|
11
|
+
- Biasanya menyediakan maklumat seperti Pengesahan (Authentication).
|
12
|
+
- Selector (selector)
|
13
|
+
- Tetapkan sasaran sebagai selector untuk mengambil nilai kandungan tertentu dari laman web.
|
@@ -0,0 +1,43 @@
|
|
1
|
+
# local-graphql-mutate
|
2
|
+
|
3
|
+
これはサーバーから提供されるGraphQL mutate APIを呼び出すタスクです。
|
4
|
+
MutationQueryを作成する際、変数の処理は次の2つの方法で行うことができ、方法2の使用をお勧めします。
|
5
|
+
|
6
|
+
方法1. シナリオコンテキストのデータや[スクリプト内蔵変数](../concept/script-internal-variables.md)などを活用できます。
|
7
|
+
この方法は文字列変数を適用する際に適しています。
|
8
|
+
|
9
|
+
```graphql
|
10
|
+
mutation {
|
11
|
+
syncAllMarketplaceOrder(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
12
|
+
...
|
13
|
+
}
|
14
|
+
|
15
|
+
removeTagFromObject(tag: "${this.data.tag}") {
|
16
|
+
...
|
17
|
+
}
|
18
|
+
}
|
19
|
+
```
|
20
|
+
|
21
|
+
方法2. 使用する変数を`variables`に指定し、GraphQL変数処理方法を使用します。variablesの値はシナリオコンテキストのデータに対するアクセサとして指定できます。
|
22
|
+
この方法はオブジェクト型変数を適用する際に適しています。
|
23
|
+
|
24
|
+
```graphql
|
25
|
+
mutation($fromDate: String!, $toDate: String!) {
|
26
|
+
syncAllMarketplaceOrder(fromDate: $fromDate, toDate: $toDate) {
|
27
|
+
...
|
28
|
+
}
|
29
|
+
|
30
|
+
removeTagFromObject(tag: $tag) {
|
31
|
+
...
|
32
|
+
}
|
33
|
+
}
|
34
|
+
```
|
35
|
+
|
36
|
+
## パラメータ
|
37
|
+
|
38
|
+
- mutation
|
39
|
+
- GraphQL mutationクエリを入力します。
|
40
|
+
|
41
|
+
- variables
|
42
|
+
- GraphQLクエリで使用される変数を定義します。
|
43
|
+
- キーは変数の名前を指定し、値には変数値に対応するデータアクセサを設定します。
|
@@ -0,0 +1,44 @@
|
|
1
|
+
# local-graphql-mutate
|
2
|
+
|
3
|
+
서버에서 제공하는 graphql mutate API를 호출하는 태스크이다.
|
4
|
+
MutationQuery를 작성할 때, 변수 처리는 다음과 같이 두 가지 방법으로 가능하며, 방법 2를 사용하기를 권장한다.
|
5
|
+
|
6
|
+
방법 1. 시나리오 컨텍스트의 data와 variables등 [스크립트 내장변수](../concept/script-internal-variables.md)를 활용할 수 있다.
|
7
|
+
이 방법은 문자열 변수를 적용할 때 적합하다.
|
8
|
+
|
9
|
+
```
|
10
|
+
mutation {
|
11
|
+
syncAllMarketplaceOrder(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
12
|
+
...
|
13
|
+
}
|
14
|
+
|
15
|
+
removeTagFromObject(tag: "${this.data.tag}") {
|
16
|
+
...
|
17
|
+
}
|
18
|
+
}
|
19
|
+
```
|
20
|
+
|
21
|
+
방법 2. varibles에 사용할 변수를 지정하고, graphql 변수 처리방법을 사용한다. variables의 값은 시나리오 컨텍스트의 data 에 대한 accessor로 지정할 수 있다.
|
22
|
+
이 방법은 객체형 변수를 적용할 때 적합하다.
|
23
|
+
|
24
|
+
```
|
25
|
+
mutation($fromDate: String!, $toDate: String!) {
|
26
|
+
syncAllMarketplaceOrder(fromDate: $fromDate, toDate: $toDate) {
|
27
|
+
...
|
28
|
+
}
|
29
|
+
|
30
|
+
removeTagFromObject(tag: $tag) {
|
31
|
+
...
|
32
|
+
}
|
33
|
+
}
|
34
|
+
```
|
35
|
+
|
36
|
+
## parameters
|
37
|
+
|
38
|
+
- mutation
|
39
|
+
|
40
|
+
- graphql mutation 쿼리를 입력한다.
|
41
|
+
|
42
|
+
- variables
|
43
|
+
- graphql query에서 사용될 변수를 정의한다.
|
44
|
+
- key예는 변수의 이름을 지정하며, value에는 변수값에 해당하는 data accessor를 설정한다.
|
@@ -1,12 +1,10 @@
|
|
1
|
-
#
|
1
|
+
# local-graphql-mutate
|
2
2
|
|
3
|
-
|
4
|
-
MutationQuery를 작성할 때, 변수 처리는 다음과 같이 두 가지 방법으로 가능하며, 방법 2를 사용하기를 권장한다.
|
3
|
+
This is a task that calls the GraphQL mutate API provided by the server. When constructing a MutationQuery, variable processing can be done in two ways, and it is recommended to use method 2.
|
5
4
|
|
6
|
-
|
7
|
-
이 방법은 문자열 변수를 적용할 때 적합하다.
|
5
|
+
Method 1: Utilize [Script Internal Variables](../concept/script-internal-variables.md), such as data and variables in the scenario context. This method is suitable for applying string variables.
|
8
6
|
|
9
|
-
```
|
7
|
+
```graphql
|
10
8
|
mutation {
|
11
9
|
syncAllMarketplaceOrder(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
12
10
|
...
|
@@ -18,10 +16,9 @@ mutation {
|
|
18
16
|
}
|
19
17
|
```
|
20
18
|
|
21
|
-
|
22
|
-
이 방법은 객체형 변수를 적용할 때 적합하다.
|
19
|
+
Method 2: Specify the variables to be used in `variables` and use the GraphQL variable processing method. The value of variables can be specified as a data accessor for the scenario context. This method is suitable for applying object-type variables.
|
23
20
|
|
24
|
-
```
|
21
|
+
```graphql
|
25
22
|
mutation($fromDate: String!, $toDate: String!) {
|
26
23
|
syncAllMarketplaceOrder(fromDate: $fromDate, toDate: $toDate) {
|
27
24
|
...
|
@@ -33,12 +30,11 @@ mutation($fromDate: String!, $toDate: String!) {
|
|
33
30
|
}
|
34
31
|
```
|
35
32
|
|
36
|
-
##
|
33
|
+
## Parameters
|
37
34
|
|
38
35
|
- mutation
|
39
|
-
|
40
|
-
- graphql mutation 쿼리를 입력한다.
|
36
|
+
- Input the GraphQL mutation query.
|
41
37
|
|
42
38
|
- variables
|
43
|
-
-
|
44
|
-
-
|
39
|
+
- Define the variables to be used in the GraphQL query.
|
40
|
+
- Specify the variable name as the key and set the data accessor corresponding to the variable value in the value.
|
@@ -0,0 +1,40 @@
|
|
1
|
+
# local-graphql-mutate
|
2
|
+
|
3
|
+
Ini adalah tugasan yang memanggil API mutate GraphQL yang disediakan oleh pelayan. Apabila membina MutationQuery, pemprosesan pembolehubah boleh dilakukan dengan dua cara, dan disyorkan untuk menggunakan cara 2.
|
4
|
+
|
5
|
+
Cara 1: Memanfaatkan [Pembolehubah Dalaman Skrip](../concept/script-internal-variables.md), seperti data dan pembolehubah dalam konteks senario. Cara ini sesuai untuk mengguna pakai pembolehubah rentetan.
|
6
|
+
|
7
|
+
```graphql
|
8
|
+
mutation {
|
9
|
+
syncAllMarketplaceOrder(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
10
|
+
...
|
11
|
+
}
|
12
|
+
|
13
|
+
removeTagFromObject(tag: "${this.data.tag}") {
|
14
|
+
...
|
15
|
+
}
|
16
|
+
}
|
17
|
+
```
|
18
|
+
|
19
|
+
Cara 2: Tentukan pembolehubah yang hendak digunakan dalam `variables` dan gunakan kaedah pemprosesan pembolehubah GraphQL. Nilai pembolehubah boleh ditentukan sebagai pembolehubah data untuk konteks senario. Cara ini sesuai untuk mengguna pakai pembolehubah jenis objek.
|
20
|
+
|
21
|
+
```graphql
|
22
|
+
mutation($fromDate: String!, $toDate: String!) {
|
23
|
+
syncAllMarketplaceOrder(fromDate: $fromDate, toDate: $toDate) {
|
24
|
+
...
|
25
|
+
}
|
26
|
+
|
27
|
+
removeTagFromObject(tag: $tag) {
|
28
|
+
...
|
29
|
+
}
|
30
|
+
}
|
31
|
+
```
|
32
|
+
|
33
|
+
## parameter
|
34
|
+
|
35
|
+
- mutation
|
36
|
+
- Masukkan kueri mutasi GraphQL.
|
37
|
+
|
38
|
+
- variables
|
39
|
+
- Tentukan pembolehubah yang hendak digunakan dalam kueri GraphQL.
|
40
|
+
- Nyatakan nama pembolehubah sebagai kunci dan tetapkan akses data yang sepadan dengan nilai pembolehubah dalam nilai.
|
@@ -0,0 +1,40 @@
|
|
1
|
+
# local-graphql-mutate
|
2
|
+
|
3
|
+
这是调用服务器提供的GraphQL mutate API的任务。在构建MutationQuery时,可以通过两种方式进行变量处理,建议使用方法2。
|
4
|
+
|
5
|
+
方法1:利用[脚本内部变量](../concept/script-internal-variables.md),例如在场景上下文中的数据和变量。此方法适用于应用字符串变量。
|
6
|
+
|
7
|
+
```graphql
|
8
|
+
mutation {
|
9
|
+
syncAllMarketplaceOrder(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
10
|
+
...
|
11
|
+
}
|
12
|
+
|
13
|
+
removeTagFromObject(tag: "${this.data.tag}") {
|
14
|
+
...
|
15
|
+
}
|
16
|
+
}
|
17
|
+
```
|
18
|
+
|
19
|
+
方法2:在`variables`中指定要使用的变量,并使用GraphQL变量处理方法。变量的值可以指定为场景上下文的数据访问器。此方法适用于应用对象类型变量。
|
20
|
+
|
21
|
+
```graphql
|
22
|
+
mutation($fromDate: String!, $toDate: String!) {
|
23
|
+
syncAllMarketplaceOrder(fromDate: $fromDate, toDate: $toDate) {
|
24
|
+
...
|
25
|
+
}
|
26
|
+
|
27
|
+
removeTagFromObject(tag: $tag) {
|
28
|
+
...
|
29
|
+
}
|
30
|
+
}
|
31
|
+
```
|
32
|
+
|
33
|
+
## 参数
|
34
|
+
|
35
|
+
- mutation
|
36
|
+
- 输入GraphQL mutate查询。
|
37
|
+
|
38
|
+
- variables
|
39
|
+
- 定义在GraphQL查询中使用的变量。
|
40
|
+
- 将变量的名称指定为键,并在值中设置与变量值相对应的数据访问器。
|
@@ -0,0 +1,42 @@
|
|
1
|
+
# local-graphql-query
|
2
|
+
|
3
|
+
これはサーバーから提供されるGraphQL query APIを呼び出すタスクです。Queryを作成する際、変数の処理は次の2つの方法で行うことができ、方法2の使用をお勧めします。
|
4
|
+
|
5
|
+
方法1. シナリオコンテキストのデータや[スクリプト内蔵変数](../concept/script-internal-variables.md)などを活用できます。
|
6
|
+
この方法は文字列変数を適用する際に適しています。
|
7
|
+
|
8
|
+
```graphql
|
9
|
+
query {
|
10
|
+
fetchWorkOrderHistory(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
11
|
+
...
|
12
|
+
}
|
13
|
+
|
14
|
+
searchObjectWithTag(tag: "${this.data.tag}") {
|
15
|
+
...
|
16
|
+
}
|
17
|
+
}
|
18
|
+
```
|
19
|
+
|
20
|
+
方法2. 使用する変数を`variables`に指定し、GraphQL変数処理方法を使用します。variablesの値はシナリオコンテキストのデータに対するアクセサとして指定できます。
|
21
|
+
この方法はオブジェクト型変数を適用する際に適しています。
|
22
|
+
|
23
|
+
```graphql
|
24
|
+
query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag: String!) {
|
25
|
+
boards(filters: $filters, sortings: $sortings, pagination: $pagination) {
|
26
|
+
...
|
27
|
+
}
|
28
|
+
|
29
|
+
searchObjectWithTag(tag: $tag) {
|
30
|
+
...
|
31
|
+
}
|
32
|
+
}
|
33
|
+
```
|
34
|
+
|
35
|
+
## パラメータ
|
36
|
+
|
37
|
+
- query
|
38
|
+
- GraphQL queryを入力します。
|
39
|
+
|
40
|
+
- variables
|
41
|
+
- GraphQL queryで使用される変数を定義します。
|
42
|
+
- キーは変数の名前を指定し、値には変数値に対応するデータアクセサを設定します。
|
@@ -0,0 +1,44 @@
|
|
1
|
+
# local-graphql-query
|
2
|
+
|
3
|
+
서버에서 제공하는 graphql query API를 호출하는 태스크이다.
|
4
|
+
Query를 작성할 때, 변수 처리는 다음과 같이 두 가지 방법으로 가능하며, 방법 2를 사용하기를 권장한다.
|
5
|
+
|
6
|
+
방법 1. 시나리오 컨텍스트의 data와 variables등 [스크립트 내장변수](../concept/script-internal-variables.md)를 활용할 수 있다.
|
7
|
+
이 방법은 문자열 변수를 적용할 때 적합하다.
|
8
|
+
|
9
|
+
```
|
10
|
+
query {
|
11
|
+
fetchWorkOrderHistory(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
12
|
+
...
|
13
|
+
}
|
14
|
+
|
15
|
+
searchObjectWithTag(tag: "${this.data.tag}") {
|
16
|
+
...
|
17
|
+
}
|
18
|
+
}
|
19
|
+
```
|
20
|
+
|
21
|
+
방법 2. varibles에 사용할 변수를 지정하고, graphql 변수 처리방법을 사용한다. variables의 값은 시나리오 컨텍스트의 data 에 대한 accessor로 지정할 수 있다.
|
22
|
+
이 방법은 객체형 변수를 적용할 때 적합하다.
|
23
|
+
|
24
|
+
```
|
25
|
+
query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag: String!) {
|
26
|
+
boards(filters: $filters, sortings: $sortings, pagination: $pagination) {
|
27
|
+
...
|
28
|
+
}
|
29
|
+
|
30
|
+
searchObjectWithTag(tag: $tag) {
|
31
|
+
...
|
32
|
+
}
|
33
|
+
}
|
34
|
+
```
|
35
|
+
|
36
|
+
## parameters
|
37
|
+
|
38
|
+
- query
|
39
|
+
|
40
|
+
- graphql query를 입력한다.
|
41
|
+
|
42
|
+
- variables
|
43
|
+
- graphql query에서 사용될 변수를 정의한다.
|
44
|
+
- key예는 변수의 이름을 지정하며, value에는 변수값에 해당하는 data accessor를 설정한다.
|
@@ -1,12 +1,10 @@
|
|
1
|
-
#
|
1
|
+
# local-graphql-query
|
2
2
|
|
3
|
-
|
4
|
-
Query를 작성할 때, 변수 처리는 다음과 같이 두 가지 방법으로 가능하며, 방법 2를 사용하기를 권장한다.
|
3
|
+
This is a task that calls the GraphQL query API provided by the server. When creating a query, variable processing can be done in two ways, and it is recommended to use method 2.
|
5
4
|
|
6
|
-
|
7
|
-
이 방법은 문자열 변수를 적용할 때 적합하다.
|
5
|
+
Method 1: Utilize [Script Internal Variables](../concept/script-internal-variables.md), such as data and variables in the scenario context. This method is suitable for applying string variables.
|
8
6
|
|
9
|
-
```
|
7
|
+
```graphql
|
10
8
|
query {
|
11
9
|
fetchWorkOrderHistory(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
12
10
|
...
|
@@ -18,10 +16,9 @@ query {
|
|
18
16
|
}
|
19
17
|
```
|
20
18
|
|
21
|
-
|
22
|
-
이 방법은 객체형 변수를 적용할 때 적합하다.
|
19
|
+
Method 2: Specify the variables to be used in `variables` and use the GraphQL variable processing method. The value of variables can be specified as a data accessor for the scenario context. This method is suitable for applying object-type variables.
|
23
20
|
|
24
|
-
```
|
21
|
+
```graphql
|
25
22
|
query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag: String!) {
|
26
23
|
boards(filters: $filters, sortings: $sortings, pagination: $pagination) {
|
27
24
|
...
|
@@ -33,12 +30,11 @@ query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag:
|
|
33
30
|
}
|
34
31
|
```
|
35
32
|
|
36
|
-
##
|
33
|
+
## Parameters
|
37
34
|
|
38
35
|
- query
|
39
|
-
|
40
|
-
- graphql query를 입력한다.
|
36
|
+
- Input the GraphQL query.
|
41
37
|
|
42
38
|
- variables
|
43
|
-
-
|
44
|
-
-
|
39
|
+
- Define the variables to be used in the GraphQL query.
|
40
|
+
- Specify the variable name as the key and set the data accessor corresponding to the variable value in the value.
|
@@ -0,0 +1,41 @@
|
|
1
|
+
|
2
|
+
# local-graphql-query
|
3
|
+
|
4
|
+
Ini adalah tugasan yang memanggil API query GraphQL yang disediakan oleh pelayan. Apabila membuat kueri, pemprosesan pembolehubah boleh dilakukan dengan dua cara, dan disyorkan untuk menggunakan cara 2.
|
5
|
+
|
6
|
+
Cara 1: Memanfaatkan [Pembolehubah Dalaman Skrip](../concept/script-internal-variables.md), seperti data dan pembolehubah dalam konteks senario. Cara ini sesuai untuk mengguna pakai pembolehubah rentetan.
|
7
|
+
|
8
|
+
```graphql
|
9
|
+
query {
|
10
|
+
fetchWorkOrderHistory(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
11
|
+
...
|
12
|
+
}
|
13
|
+
|
14
|
+
searchObjectWithTag(tag: "${this.data.tag}") {
|
15
|
+
...
|
16
|
+
}
|
17
|
+
}
|
18
|
+
```
|
19
|
+
|
20
|
+
Cara 2: Tentukan pembolehubah yang hendak digunakan dalam `variables` dan gunakan kaedah pemprosesan pembolehubah GraphQL. Nilai pembolehubah boleh ditentukan sebagai pembolehubah data untuk konteks senario. Cara ini sesuai untuk mengguna pakai pembolehubah jenis objek.
|
21
|
+
|
22
|
+
```graphql
|
23
|
+
query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag: String!) {
|
24
|
+
boards(filters: $filters, sortings: $sortings, pagination: $pagination) {
|
25
|
+
...
|
26
|
+
}
|
27
|
+
|
28
|
+
searchObjectWithTag(tag: $tag) {
|
29
|
+
...
|
30
|
+
}
|
31
|
+
}
|
32
|
+
```
|
33
|
+
|
34
|
+
## parameter
|
35
|
+
|
36
|
+
- query
|
37
|
+
- Masukkan kueri GraphQL.
|
38
|
+
|
39
|
+
- variables
|
40
|
+
- Tentukan pembolehubah yang hendak digunakan dalam kueri GraphQL.
|
41
|
+
- Nyatakan nama pembolehubah sebagai kunci dan tetapkan akses data yang sepadan dengan nilai pembolehubah dalam nilai.
|
@@ -0,0 +1,40 @@
|
|
1
|
+
# local-graphql-query
|
2
|
+
|
3
|
+
这是调用服务器提供的GraphQL query API的任务。在构建查询时,变量处理可以通过两种方式进行,建议使用方法2。
|
4
|
+
|
5
|
+
方法1:利用[脚本内部变量](../concept/script-internal-variables.md),例如在场景上下文中的数据和变量。此方法适用于应用字符串变量。
|
6
|
+
|
7
|
+
```graphql
|
8
|
+
query {
|
9
|
+
fetchWorkOrderHistory(fromDate: "${this.variables.fromDate}", toDate: "${this.variables.toDate}") {
|
10
|
+
...
|
11
|
+
}
|
12
|
+
|
13
|
+
searchObjectWithTag(tag: "${this.data.tag}") {
|
14
|
+
...
|
15
|
+
}
|
16
|
+
}
|
17
|
+
```
|
18
|
+
|
19
|
+
方法2:在`variables`中指定要使用的变量,并使用GraphQL变量处理方法。变量的值可以指定为场景上下文的数据访问器。此方法适用于应用对象类型变量。
|
20
|
+
|
21
|
+
```graphql
|
22
|
+
query($filters: [Filter!], $sortings: [Sorting!], $pagination: Pagination, tag: String!) {
|
23
|
+
boards(filters: $filters, sortings: $sortings, pagination: $pagination) {
|
24
|
+
...
|
25
|
+
}
|
26
|
+
|
27
|
+
searchObjectWithTag(tag: $tag) {
|
28
|
+
...
|
29
|
+
}
|
30
|
+
}
|
31
|
+
```
|
32
|
+
|
33
|
+
## 参数
|
34
|
+
|
35
|
+
- query
|
36
|
+
- 输入GraphQL查询。
|
37
|
+
|
38
|
+
- variables
|
39
|
+
- 定义在GraphQL查询中使用的变量。
|
40
|
+
- 键是变量的名称,值是与变量值相对应的数据访问器。
|