You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/framework/svelte/guides/form-composition.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ A common criticism of TanStack Form is its verbosity out-of-the-box. While this
7
7
8
8
As a result, while `form.Field` enables the most powerful and flexible usage of TanStack Form, we provide APIs that wrap it and make your application code less verbose.
9
9
10
-
## Custom Form Runes
10
+
## Custom Form Methods
11
11
12
-
The most powerful way to compose forms is to create custom form runes. This allows you to create a form rune that is tailored to your application's needs, including pre-bound custom UI components and more.
12
+
The most powerful way to compose forms is to create custom form methods. This allows you to create a form method that is tailored to your application's needs, including pre-bound custom UI components and more.
13
13
14
-
At its most basic, `createFormCreator` is a function that returns a `createAppForm`rune.
14
+
At its most basic, `createFormCreator` is a function that returns a `createAppForm`method.
15
15
16
-
> This un-customized `createAppForm`rune is identical to `createForm`, but that will quickly change as we add more options to `createFormCreator`.
16
+
> This un-customized `createAppForm`method is identical to `createForm`, but that will quickly change as we add more options to `createFormCreator`.
@@ -327,12 +327,12 @@ We can now use these grouped fields in any form that implements the required fie
327
327
## Tree-shaking form and field components
328
328
329
329
While the above examples are great for getting started, they're not ideal for certain use-cases where you might have hundreds of form and field components.
330
-
In particular, you may not want to include all of your form and field components in the bundle of every file that uses your form rune.
330
+
In particular, you may not want to include all of your form and field components in the bundle of every file that uses your form method.
331
331
332
332
To solve this, you can use dynamic imports with Svelte's component loading:
0 commit comments