From 6add2b0648f4574c30a3e943fbc34ffeef09ef7c Mon Sep 17 00:00:00 2001 From: Hunter Johnston <64506580+huntabyte@users.noreply.github.com> Date: Wed, 21 Feb 2024 11:36:57 -0500 Subject: [PATCH] docs: fix field typo (#140) --- sites/docs/content/components/field.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs/content/components/field.md b/sites/docs/content/components/field.md index d2bd82a..4be79fc 100644 --- a/sites/docs/content/components/field.md +++ b/sites/docs/content/components/field.md @@ -49,7 +49,7 @@ type SlotProps, U extends FormPath> = { Since the `Field` component doesn't render any HTML elements, it's a common practice to create a wrapper component around it to have consistent styling and behavior across your forms. -For example, you may always want to render the [ValidationError](/docs/components/validation-error) component for every field. Instead of manually including it every time, you can create a wrapper `` component that includes it automatically. +For example, you may always want to render the [FieldErrors](/docs/components/field-errors) component for every field. Instead of manually including it every time, you can create a wrapper `` component that includes it automatically. To maintain the type safety of the component, we'll need to use some generics, which eslint sometimes complains about, so if you see a warning, it's likely a false positive and you can ignore it.