-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3 docs #11
base: johnrom/v3
Are you sure you want to change the base?
v3 docs #11
Conversation
…for intellisense & FieldRegistry.
…fix checkbox values.
… isn't working for array types.
…NameOf<Values>`, allowing fields to infer back and forth. Need to test features within AsFields and ComponentFields and confirm we can build highly reusable fields in this API. Then, need to do a pass to see if we can make the types more readable and also ensure backwards compatibility.
… values in order to intersect all possible names with possible names for a given value type.
Need to expand functionality to component= and FieldArray.
…e<FieldProps> and ComponentType<ExtraProps>.
…hen using ExtraProps I recommend wrapping the component, as the component cannot be configured within as= or component=, like for parse, format, validate.
… typescript casts internally.
…in exchange for stronger types.
… But something broke...
# Conflicts: # packages/formik-native/package.json
…lish # Conflicts: # app/package.json # packages/formik-native/package.json # packages/formik/package.json # packages/formik/src/Formik.tsx # packages/formik/src/hooks/hooks.ts # packages/formik/src/types.tsx
…amples`, start converting examples to TypeScript.
…docs-and-packages
…lex` and integrate state documentation.
…cs around to improve reusability.
…to keep going, updating the docs on all apis, components, examples and guides.
…nd-batching # Conflicts: # package.json # packages/formik/package.json # packages/formik/src/Field.tsx # packages/formik/src/Formik.tsx # packages/formik/src/FormikContext.tsx # packages/formik/src/helpers/field-helpers.ts # packages/formik/src/hooks/hooks.ts # packages/formik/src/hooks/useFormikSubscriptions.ts # packages/formik/src/index.tsx # packages/formik/src/types.tsx # yarn.lock
…nd-packages # Conflicts: # package.json # packages/dev-native/__generated__/AppEntry.js # packages/dev-web/helpers/parse-format-helpers.ts # packages/dev-web/pages/fixtures/type-tests.tsx # packages/dev-web/pages/tutorial/strongly-typed.tsx # packages/formik/src/types.tsx # yarn.lock
# Conflicts: # packages/formik/src/types.tsx
…ified-docs-and-packages. Publish 3.1.0-types14.
Hey @johnrom - apologies for the ping - is there anything the community (EG: me) can do to help with the potential v3 of Formik? As I understand it, reading through GitHub issues and convos, this has been primarily solo work on your end based on prior conversations with Jared. However, I'm also under the understanding that you do not have access to the Formik repo itself. Would you potentially be open to discussing (via DMs, a call, or GH issues/PR chat) what work you've done on v3, how someone could pick up your work, and how we could potentially start a dedicated org/repo for Again, apologies for the ping. Just trying to figure out next best steps for my org and have not been ecstatic about alternatives to Formik. |
Update the docs for Formik, relying heavily on importing code snippets from the codesandbox examples using
nmbl/code-snippets
.