Parse Format PR Review Changes

[johnrom]

Fixes items in review for #2255

I didn't actually get a chance to test it on a real project yet. @jaredpalmer do you use npm link?

I think last time I was having issues with "two reacts" when using npm link. Maybe that's been fixed since then.

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/jared/formik-docs/q73cgnjr8
✅ Preview: https://formik-docs-git-fork-johnrom-johnrom-parse-format.jared.now.sh

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 1b3d5af:

Sandbox	Source
Formik TypeScript Playground	Configuration

[johnrom]

Added a small change removing parse and format props from the underlying <input /> when not passed a complex component. I honestly don't think we should be passing them to complex components either, but didn't have time to think it through so I left it for now.

I was having the double-react issue again. I switched to Yarn, which seemed to help once every few builds, but then I'd get the same error again. Basically, after running yarn link (/packages/formik), yarn link formik (../formik-dev), yarn build (/) and yarn start (../formik-dev), I had to delete /node_modules because the linked formik would traverse its real path's node_modules and find a second react in the lerna root. Is there a better workflow for this?

[jaredpalmer]

@johnrom re: lerna, i can commit a tsdx playground that uses parcel to alias the react install