feat: use setInitialState for async initialization

[amythos]

usage

---

module StateLenses = [%lenses
  type state = {
    description: string,
    title: string,
    acceptTerms: bool,
  }
];
module PostAddForm = ReFormNext.Make(StateLenses);

[@react.component]
let make = () => {
  let {state, submit, getFieldState, handleChange, setValues}: PostAddForm.api =
    PostAddForm.use(
      ~schema={
        PostAddForm.Validation.Schema([|
          Custom(
            Title,
            values =>
              Js.String.length(values.title) > 20
                ? Error("Keep it short!") : Valid,
          ),
          Custom(
            Description,
            values =>
              values.description == "" ? Error("Can't be empty") : Valid,
          ),
          Custom(
            AcceptTerms,
            values =>
              values.acceptTerms == false
                ? Error("You must accept all the terms") : Valid,
          ),
        |]);
      },
      ~onSubmit=
        ({state}) => {
          mutate(
            ~variables=
              PostAddMutationConfig.make(
                ~title=state.values.title,
                ~description=state.values.description,
                (),
              )##variables,
            (),
          )
          |> Js.Promise.then_(result =>
               setResult(_ => Some(result)) |> Js.Promise.resolve
             )
          |> ignore;

          None;
        },
      ~initialState={title: "", description: "", acceptTerms: false},
      (),
    );
  
  React.useEffect0(() => {
      fetchDefaultState(fetchUrl, state => setValues(state));
  });
};

[fakenickels]

Thanks, this makes a lot of sense!

[fakenickels]

I think we can actually create a helper called setValues

[amythos]

i think that setValues means set all values passed in, and setInitialState means won't set the value when its fieldState is not Pristine, maybe we can call it setinitialValues

[fakenickels]

that makes sense, I'll take a better look soon so we can get it merged

[amythos]

hello @fakenickels would you have time to merge this

[fakenickels]

Sorry about the delay, the past few days have we have been a bit busy. I'll gonna finish the review today and give you a better feedback soon

[fakenickels]

With setValues I don't think this is necessary

[fakenickels]

hmm looking the ResetForm branch changes I got it now

[fakenickels]

@amythos This looks good, but for the next releases we are going to try to make ReForm as similar as possible to Formik to ease adoption. So in Formik there is no setInitialValues, we just have a setValues. So before merging this PR we would like to have the handlers also named setValues and no initValues on the state, if the user needs to resetTheForm and apply the initialState the user will just call reset and call setValues as well.

[fakenickels]

let's call this setValues now

[amythos]

@fakenickels now we have setValues for set the whole state, and setFieldValue for the single field

[fakenickels]

Thank you for your time and effort @amythos , we'll be releasing this to NPM soon

[fakenickels]

@all-contributors please add @amythos for code

[allcontributors]

@fakenickels

I've put up a pull request to add @amythos! 🎉