Skip to content
Source
Sign inSign up
TanStack/form

[Docs] UI Library Support #473

Send to my agent
Closedcrutchcorn(GitHub profile, opens in a new tab) opened this issue 7 comments

It would be awesome to have a docs page akin to the following:

https://houseform.dev/guides/ui-libraries.html

https://vee-validate.logaretm.com/v4/examples/ui-libraries/

TLDR: TanStack Form should support any UI library as if they were purpose-built for one-another.

It would also be ideal to add examples for a few popular UI libraries for each respective framework (Vuetify, MUI, etc)

  1. crutchcorn(GitHub profile, opens in a new tab) added labelsgood first issue

  2. crutchcorn(GitHub profile, opens in a new tab) added labelstype: docs

  3. crutchcorn(GitHub profile, opens in a new tab) added labelstype: enhancement

  4. Could you please assign me this issue?

  5. @crutchcorn Sir, akin to tanstack, i have to add frameworks which supports it, right?

  6. Hey @crutchcorn please assign this to me, I have create a pull request with 2 options Material-ui and Mantine https://github.com/TanStack/form/pull/536 Thank you

  7. @enyelsequeira Thanks for adding the docs! It leaves one question open though, how to generically wrap components, i.e. wrapping a UI library component in a shared module? The docs are a bit terse here, I might also still think too much in patterns used by Final-Form, which I would like to replace.

    The examples in your update require creation of a form instance by calling useForm to get the Field component. This would mean we could only build factory functions to create components… I would assume you can use the useField hook to wrap a component come manually, or does TanStack Form export a generic Field component so that we can always use the render prop style?

    Thanks for making this, I'm really loving what you and everyone else is making possible for us with TanStack!

  8. @thuringia let's open a new issue to track this :)

  9. @thuringia did you manage to open an issue for this? Running into the same issue.

Sign in to join this conversation.