Add emails REST API doc. #712
Annotations
10 errors and 11 warnings
Vale:
docs/rest_api/emails.rst#L109
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'http' instead of 'HTTP'.
Raw Output:
{"message": "[Vale.Terms] Use 'http' instead of 'HTTP'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 109, "column": 1}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L143
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'bcc' instead of 'BCC'.
Raw Output:
{"message": "[Vale.Terms] Use 'bcc' instead of 'BCC'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 143, "column": 45}}}, "severity": "ERROR"}
|
Vale
reviewdog: Too many results (annotations) in diff.
You may miss some annotations due to GitHub limitation for annotation created by logging command.
Please check GitHub Actions log console to see all results.
Limitation:
- 10 warning annotations and 10 error annotations per step
- 50 annotations per job (sum of annotations from all the steps)
- 50 annotations per run (separate from the job annotations, these annotations aren't created by users)
Source: https://github.community/t5/GitHub-Actions/Maximum-number-of-annotations-that-can-be-created-using-GitHub/m-p/39085
|
Vale:
docs/rest_api/emails.rst#L223
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'Segment Email' instead of 'segment Email'.
Raw Output:
{"message": "[Vale.Terms] Use 'Segment Email' instead of 'segment Email'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 223, "column": 54}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L320
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'http' instead of 'HTTP'.
Raw Output:
{"message": "[Vale.Terms] Use 'http' instead of 'HTTP'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 320, "column": 1}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L341
[vale] reported by reviewdog ๐ถ
[Vale.Spelling] Did you really mean 'asc'?
Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'asc'?", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 341, "column": 38}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L381
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'http' instead of 'HTTP'.
Raw Output:
{"message": "[Vale.Terms] Use 'http' instead of 'HTTP'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 381, "column": 1}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L386
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'post' instead of 'Post'.
Raw Output:
{"message": "[Vale.Terms] Use 'post' instead of 'Post'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 386, "column": 3}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L408
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'bcc' instead of 'BCC'.
Raw Output:
{"message": "[Vale.Terms] Use 'bcc' instead of 'BCC'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 408, "column": 45}}}, "severity": "ERROR"}
|
Vale:
docs/rest_api/emails.rst#L472
[vale] reported by reviewdog ๐ถ
[Vale.Terms] Use 'Segment Email' instead of 'segment Email'.
Raw Output:
{"message": "[Vale.Terms] Use 'Segment Email' instead of 'segment Email'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 472, "column": 54}}}, "severity": "ERROR"}
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Vale:
docs/rest_api/emails.rst#L143
[vale] reported by reviewdog ๐ถ
[Google.Acronyms] Spell out 'BCC', if it's unfamiliar to the audience.
Raw Output:
{"message": "[Google.Acronyms] Spell out 'BCC', if it's unfamiliar to the audience.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 143, "column": 45}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L190
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 190, "column": 50}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L191
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'landing page'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'landing page'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 191, "column": 62}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L193
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'page'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'page'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 193, "column": 57}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L206
[vale] reported by reviewdog ๐ถ
[Google.Parens] Use parentheses judiciously.
Raw Output:
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 206, "column": 49}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L217
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'page'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'page'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 217, "column": 53}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L219
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Dynamic Content' instead of 'Dynamic content'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Dynamic Content' instead of 'Dynamic content'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 219, "column": 41}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L225
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Asset' instead of 'asset'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Asset' instead of 'asset'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 225, "column": 41}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L229
[vale] reported by reviewdog ๐ถ
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Email' instead of 'email'.
Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Email' instead of 'email'.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 229, "column": 55}}}, "severity": "INFO"}
|
Vale:
docs/rest_api/emails.rst#L232
[vale] reported by reviewdog ๐ถ
[Google.Headings] 'List Emails' should use sentence-style capitalization.
Raw Output:
{"message": "[Google.Headings] 'List Emails' should use sentence-style capitalization.", "location": {"path": "docs/rest_api/emails.rst", "range": {"start": {"line": 232, "column": 1}}}, "severity": "WARNING"}
|
Loading