tabshift/payloadcms
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs: closes <strong> tags properly on jobs queue documentation (#9067)

Browse Source 
### What?

Fixes a formatting issue that prevents
payloadcms.com/docs/beta/jobs-queue/overview from displaying properly.
There were a couple `<strong>` tags in the `jobs-queue/overview` docs
that did not have proper closing `</strong>` tags.
This commit is contained in:
Tylan Davis
2024-11-07 12:42:16 -05:00
committed by GitHub
parent e907724af7
commit 1267aedfd3
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/jobs-queue/overview.mdx
View File

@@ -21,7 +21,7 @@ There are a few concepts that you should become familiarized with before using P
## Tasks
<Banner type="default">
A <strong>"Task"<strong> is a function definition that performs business logic and whose input and output are both strongly typed.
A <strong>"Task"</strong> is a function definition that performs business logic and whose input and output are both strongly typed.
</Banner>
You can register Tasks on the Payload config, and then create Jobs or Workflows that use them. Think of Tasks like tidy, isolated "functions that do one specific thing".
@@ -157,7 +157,7 @@ export const createPostHandler: TaskHandler<'createPost'> = async ({ input, job,
## Workflows
<Banner type="default">
A <strong>"Workflow"<strong> is an optional way to <em>combine multiple tasks together</em> in a way that can be gracefully retried from the point of failure.
A <strong>"Workflow"</strong> is an optional way to <em>combine multiple tasks together</em> in a way that can be gracefully retried from the point of failure.
</Banner>
They're most helpful when you have multiple tasks in a row, and you want to configure each task to be able to be retried if they fail.