Recommend a forms library in the docs?

Open
#288 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
react
Domain
documentation

Research direction

Start with the Forms section of the reason-react documentation and review how it currently addresses validation and error messages. Research whether Formik or another library fits this ecosystem, then document the recommendation; if no library is needed, add the rationale and a short demonstration as requested.

Written by the indexing model from the issue text.

Description

docs

Proposal for improving the documentation:

The "Forms" section of the ReactJS documentation recommends using additional libraries for forms validation/error messages/etc.. It also explicitly names the Formik library.

Should the reason-react documentation also make such a recommendation?

If so, which library should be recommended? Also Formik, or something else?

Or, is there no need for this in reason-react? If so, this should be mentioned in the docs as well, with a short demo of why forms not as painful as in vanilla ReactJS.

Dominant language
Reason
Stars
3.3k
Forks
344
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reasonml/reason-react

All issues in reasonml/reason-react

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.