@wix/auto_sdk_seo_content-plan-flows 1.0.0 → 1.0.2
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/build/cjs/index.d.ts +5 -3
- package/build/cjs/index.js.map +1 -1
- package/build/cjs/index.typings.d.ts +18 -9
- package/build/cjs/index.typings.js.map +1 -1
- package/build/cjs/meta.d.ts +13 -6
- package/build/cjs/meta.js.map +1 -1
- package/build/es/index.d.mts +5 -3
- package/build/es/index.mjs.map +1 -1
- package/build/es/index.typings.d.mts +18 -9
- package/build/es/index.typings.mjs.map +1 -1
- package/build/es/meta.d.mts +13 -6
- package/build/es/meta.mjs.map +1 -1
- package/build/internal/cjs/index.d.ts +5 -3
- package/build/internal/cjs/index.typings.d.ts +18 -9
- package/build/internal/cjs/meta.d.ts +13 -6
- package/build/internal/es/index.d.mts +5 -3
- package/build/internal/es/index.typings.d.mts +18 -9
- package/build/internal/es/meta.d.mts +13 -6
- package/package.json +2 -2
|
@@ -8,7 +8,10 @@ import { NonNullablePaths } from '@wix/sdk-types';
|
|
|
8
8
|
* minutes, so the flow runs asynchronously and reports its progress in `status`.
|
|
9
9
|
*
|
|
10
10
|
* A flow doesn't run to completion on its own. It stops at `KEYWORD_RESEARCH`
|
|
11
|
-
* and waits for a call to Create Content Plan before it continues.
|
|
11
|
+
* and waits for a call to Create Content Plan before it continues. The flow
|
|
12
|
+
* reaches `KEYWORD_RESEARCH` when keyword research starts, so check that the
|
|
13
|
+
* research finished with Get Site Keyword Research before you call Create
|
|
14
|
+
* Content Plan.
|
|
12
15
|
*/
|
|
13
16
|
interface ContentPlanFlow {
|
|
14
17
|
/**
|
|
@@ -32,7 +35,8 @@ interface ContentPlanFlow {
|
|
|
32
35
|
*
|
|
33
36
|
* The status advances on its own as generation progresses, except at
|
|
34
37
|
* `KEYWORD_RESEARCH`, where the flow waits for a call to Create Content
|
|
35
|
-
* Plan.
|
|
38
|
+
* Plan. Keyword research may still be running at that point; its own
|
|
39
|
+
* status is on Get Site Keyword Research.
|
|
36
40
|
*/
|
|
37
41
|
status?: StatusWithLiterals;
|
|
38
42
|
/**
|
|
@@ -53,9 +57,10 @@ interface ContentPlanFlow {
|
|
|
53
57
|
*/
|
|
54
58
|
statusAdditionalData?: Record<string, any> | null;
|
|
55
59
|
/**
|
|
56
|
-
* ID of the keyword research the flow
|
|
60
|
+
* ID of the keyword research the flow started.
|
|
57
61
|
*
|
|
58
|
-
* Available once `status` is `KEYWORD_RESEARCH` or later.
|
|
62
|
+
* Available once `status` is `KEYWORD_RESEARCH` or later. Pass it to Get
|
|
63
|
+
* Site Keyword Research to check whether the research finished.
|
|
59
64
|
* @format GUID
|
|
60
65
|
*/
|
|
61
66
|
keywordResearchId?: string | null;
|
|
@@ -77,8 +82,10 @@ declare enum Status {
|
|
|
77
82
|
/** The site's existing content is being summarized. */
|
|
78
83
|
SITE_SUMMARY = "SITE_SUMMARY",
|
|
79
84
|
/**
|
|
80
|
-
* Keyword research
|
|
81
|
-
* Content Plan
|
|
85
|
+
* Keyword research has started, and the flow waits here until Create
|
|
86
|
+
* Content Plan is called. This status doesn't change when the research
|
|
87
|
+
* succeeds. Poll Get Site Keyword Research with `keywordResearchId`
|
|
88
|
+
* until its status is `SUCCESS`, then call Create Content Plan.
|
|
82
89
|
*/
|
|
83
90
|
KEYWORD_RESEARCH = "KEYWORD_RESEARCH",
|
|
84
91
|
/** Blog post briefs are being generated from the keyword research. */
|
|
@@ -512,7 +519,7 @@ interface AccountInfo {
|
|
|
512
519
|
* @applicableIdentity APP
|
|
513
520
|
* @fqn wix.promote.seo.content.plan.v1.ContentPlanFlowServiceV1.GetContentPlanFlow
|
|
514
521
|
*/
|
|
515
|
-
declare function getContentPlanFlow(contentPlanFlowId: string): Promise<NonNullablePaths<GetContentPlanFlowResponse, `contentPlanFlow.status`,
|
|
522
|
+
declare function getContentPlanFlow(contentPlanFlowId: string): Promise<NonNullablePaths<GetContentPlanFlowResponse, `contentPlanFlow.status`, 1>>;
|
|
516
523
|
/**
|
|
517
524
|
* Creates and starts a content plan flow for a site.
|
|
518
525
|
*
|
|
@@ -524,8 +531,10 @@ declare function getContentPlanFlow(contentPlanFlowId: string): Promise<NonNulla
|
|
|
524
531
|
* A successful response means the flow was created, not that generation
|
|
525
532
|
* succeeded. Check `status` rather than relying on the response alone.
|
|
526
533
|
*
|
|
527
|
-
* The flow stops at `KEYWORD_RESEARCH` and waits.
|
|
528
|
-
*
|
|
534
|
+
* The flow stops at `KEYWORD_RESEARCH` and waits. Once Get Site Keyword
|
|
535
|
+
* Research reports the flow's research as `SUCCESS`, call Create Content
|
|
536
|
+
* Plan to generate the blog post briefs and let the flow continue to
|
|
537
|
+
* `SUCCESS`.
|
|
529
538
|
*
|
|
530
539
|
* A failed flow is retried automatically, and each retry creates a separate
|
|
531
540
|
* flow with its own ID. The original flow keeps its `FAIL` status, so call
|
|
@@ -9,7 +9,10 @@ import '@wix/sdk-types';
|
|
|
9
9
|
* minutes, so the flow runs asynchronously and reports its progress in `status`.
|
|
10
10
|
*
|
|
11
11
|
* A flow doesn't run to completion on its own. It stops at `KEYWORD_RESEARCH`
|
|
12
|
-
* and waits for a call to Create Content Plan before it continues.
|
|
12
|
+
* and waits for a call to Create Content Plan before it continues. The flow
|
|
13
|
+
* reaches `KEYWORD_RESEARCH` when keyword research starts, so check that the
|
|
14
|
+
* research finished with Get Site Keyword Research before you call Create
|
|
15
|
+
* Content Plan.
|
|
13
16
|
*/
|
|
14
17
|
interface ContentPlanFlow {
|
|
15
18
|
/**
|
|
@@ -33,7 +36,8 @@ interface ContentPlanFlow {
|
|
|
33
36
|
*
|
|
34
37
|
* The status advances on its own as generation progresses, except at
|
|
35
38
|
* `KEYWORD_RESEARCH`, where the flow waits for a call to Create Content
|
|
36
|
-
* Plan.
|
|
39
|
+
* Plan. Keyword research may still be running at that point; its own
|
|
40
|
+
* status is on Get Site Keyword Research.
|
|
37
41
|
*/
|
|
38
42
|
status?: StatusWithLiterals;
|
|
39
43
|
/**
|
|
@@ -54,9 +58,10 @@ interface ContentPlanFlow {
|
|
|
54
58
|
*/
|
|
55
59
|
statusAdditionalData?: Record<string, any> | null;
|
|
56
60
|
/**
|
|
57
|
-
* ID of the keyword research the flow
|
|
61
|
+
* ID of the keyword research the flow started.
|
|
58
62
|
*
|
|
59
|
-
* Available once `status` is `KEYWORD_RESEARCH` or later.
|
|
63
|
+
* Available once `status` is `KEYWORD_RESEARCH` or later. Pass it to Get
|
|
64
|
+
* Site Keyword Research to check whether the research finished.
|
|
60
65
|
* @format GUID
|
|
61
66
|
*/
|
|
62
67
|
keywordResearchId?: string | null;
|
|
@@ -78,8 +83,10 @@ declare enum Status {
|
|
|
78
83
|
/** The site's existing content is being summarized. */
|
|
79
84
|
SITE_SUMMARY = "SITE_SUMMARY",
|
|
80
85
|
/**
|
|
81
|
-
* Keyword research
|
|
82
|
-
* Content Plan
|
|
86
|
+
* Keyword research has started, and the flow waits here until Create
|
|
87
|
+
* Content Plan is called. This status doesn't change when the research
|
|
88
|
+
* succeeds. Poll Get Site Keyword Research with `keywordResearchId`
|
|
89
|
+
* until its status is `SUCCESS`, then call Create Content Plan.
|
|
83
90
|
*/
|
|
84
91
|
KEYWORD_RESEARCH = "KEYWORD_RESEARCH",
|
|
85
92
|
/** Blog post briefs are being generated from the keyword research. */
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/auto_sdk_seo_content-plan-flows",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"publishConfig": {
|
|
6
6
|
"registry": "https://registry.npmjs.org/",
|
|
@@ -50,5 +50,5 @@
|
|
|
50
50
|
"fqdn": "wix.promote.seo.v1.content_plan_content_plan_flow"
|
|
51
51
|
}
|
|
52
52
|
},
|
|
53
|
-
"falconPackageHash": "
|
|
53
|
+
"falconPackageHash": "f28294f4d08da94d5234b6b37321ce1164c78c2ed38e66c280b67d2f"
|
|
54
54
|
}
|