[RFC] React Native Support about unform HOT 11 CLOSED

Maybe we can create a monorepo (as Babel and even React.js do) with two initial packages:

• packages/
  • unform
  • unform-react-native, which extends unform and adds other features.

To use in a React.js project (no breaking changes):

import { Form, Input } from "@rocketseat/unform";

// Do stuff.

And in a React Native project:

import { Form, Input, DatePicker ... } from "@rocketseat/unform-react-native";

// Do stuff.

from unform.

@lffg or can use something like styled-components do, using import {} from 'styled-components and import {} from 'styled-components/native

from unform.

I saw this discussion and I think that is not the responsibility of Unform to cares about date picker and other input types. So, my suggestion is to check if Unform is used in react native (or separate the files, like styled-components are), and so, provide properly components. For RN, only provides text Inputs (and Scope and Form too, as wrappers), and if the developer that is using Unform wants a Datepicker in the form, he can use the useField hook to register his own components.
What are your thoughts about this approach?

from unform.

But, could we begin some implementation without thinking outside TextInput's?

from unform.

@dudusotero Yeah, support for TextInput can be easily implemented. Maybe someone here can take it and open a PR.

from unform.

I personally don't think we should ship any inputs, only the interfaces to integrate the inputs as the user better desires. Sure, we might ship any logic to work with arrays and stuff, but apart from that everything is pretty much the same. Instead of shipping x components for x platforms, seems more practical/logical to ship only the base logic to implement one.

from unform.

I saw this discussion and I think that is not the responsibility of Unform to cares about date picker and other input types. So, my suggestion is to check if Unform is used in react native (or separate the files, like styled-components are), and so, provide properly components. For RN, only provides text Inputs (and Scope and Form too, as wrappers), and if the developer that is using Unform wants a Datepicker in the form, he can use the useField hook to register his own components.
What are your thoughts about this approach?

That's basically my suggestion :D A good one, I'd say!

from unform.

@zaguiini yeah. I mean, I agree with you and guess that it is a good approach to achieve Unform in RN.

from unform.

Not only RN, but for DOM as well. Making it simpler we could cut scope and areas of maintenance. That could be an extensions repository with all the custom inputs and stuff.

from unform.

+1

from unform.

Now we have support for React Native: https://unform.dev/guides/react-native

from unform.