From fa111800bdfd6cf478cf3aaa6c71387c31f698d6 Mon Sep 17 00:00:00 2001 From: Samuel Charpentier Date: Sat, 4 Oct 2025 12:35:39 -0400 Subject: [PATCH] Add link to the config method for granular control over each pipeline After it was asked as a feature, I found the documentation lacked this information in the pipelines guide. --- website/src/routes/guides/(main-concepts)/pipelines/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/routes/guides/(main-concepts)/pipelines/index.mdx b/website/src/routes/guides/(main-concepts)/pipelines/index.mdx index eb0da00c3..49ca1cf0d 100644 --- a/website/src/routes/guides/(main-concepts)/pipelines/index.mdx +++ b/website/src/routes/guides/(main-concepts)/pipelines/index.mdx @@ -44,7 +44,7 @@ const EmailSchema = v.pipe( Pipeline validation actions examine the input and, if the input does not meet a certain condition, return an issue. If the input is valid, it is returned as the output and, if present, picked up by the next action in the pipeline. -> Whenever possible, pipelines are run completely, even if an issue has occurred, to collect all possible issues. If you want to abort the pipeline early after the first issue, you need to set the `abortPipeEarly` option to `true`. Learn more about this here. +> Whenever possible, pipelines are run completely, even if an issue has occurred, to collect all possible issues. If you want to abort the pipeline early after the first issue, you need to set the `abortPipeEarly` option to `true`. Learn more about parsing configuration or the config method for a more granular control.