From a445fd889b4d4bc6784bae28be25aec4671e28f7 Mon Sep 17 00:00:00 2001 From: Carlos Jimenez Date: Tue, 23 Jun 2026 11:36:21 -0700 Subject: [PATCH] docs(philosophy): clarify 'Three.js framework adapters' to 'Three.js renderers' In the 'Controlled is Cool' section, the bullet on Non-DOM support said 'Three.js framework adapters'. Three.js is not a framework - it's a WebGL rendering library. The intended meaning was that TanStack Form's controlled-component approach works with non-DOM renderers, including Three.js. Replaced 'framework adapters' with 'renderers' to be accurate. --- docs/philosophy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/philosophy.md b/docs/philosophy.md index 9628ebbd0..5f37d1674 100644 --- a/docs/philosophy.md +++ b/docs/philosophy.md @@ -33,7 +33,7 @@ This comes with a number of advantages: - **Predictable**: You can predict the state of your form at any point in time. - **Easier testing**: You can easily test your forms by passing in values and asserting on the output. -- **Non-DOM support**: You can use TanStack Form with React Native, Three.js framework adapters, or any other framework renderer. +- **Non-DOM support**: You can use TanStack Form with React Native, Three.js renderers, or any other framework renderer. - **Enhanced conditional logic**: You can easily conditionally show/hide fields based on the form state. - **Debugging**: You can easily log the form state to the console to debug issues.