Do not use state and effects within react-jhipster

[Tcharl]

Overview of the feature request

The goal of this FR being to get rid of useState and useEffect within react-jhipster library.
The approach would be to create dedicated react elements by input kind (text, date, numbers, ...) and to keep using react-forms api, instead of using the actual reflection-intensive, not that easy to debug, React form wrapper

Motivation for or Use Case

Newest React version now forbids the use of state and effects within a library.

Related issues or PR

POC here: #19560
First react element here: jhipster/react-jhipster#87

• Checking this box is mandatory (this is just to show you read everything)

[emilpaw]

Newest React version now forbids the use of state and effects within a library.

What makes you think that? react-hook-form uses useState and useEffect so why shouldn't react-jhipster be able to do that too?

[Tcharl]

react-jhipster is a library (equivalent to a bunch of jsx.elements). useState should be at the component level.
You can see the behavior when upgrading the version of react in the library (edit the package.json, switch to latest or the same as the generator): nothing will work anymore (try with a blobfield)