JSONForms VS rfcs

I'm currently working on an Android app that requires dynamic form creation based on JSON schema. I came across the website jsonforms.io and was impressed by their framework for generating forms from JSON schema.

We use JsonForms and for multiple forms and its quite powerful & consistant

There's this cool tool called JSON Forms. Basically you specify a schema and a rudimentary form is generated based on that schema with a framework of your choosing (vue, react, angular) with no additional configuration! Sounded cool so I cloned it. Now it looks like a real time saver, but i'm concerned about how I am using an 'imported template' that will probably restrict any customization on my end.

Json Forms: https://jsonforms.io/

Yes, exactly. I did some searching after I posed the question and found this so far https://jsonforms.io/

The best way I found to build form intensive apps is using: https://jsonforms.io/ It's super declarative with JSON Schema and can be easily extended by writing custom widgets. Also it provides good balance between being "battery charged" and freedom of state management.

I agree. RJSF examples work fine but it doesn't scale well to large forms. For a similar approach but better implementation, take a look at https://jsonforms.io/ which also supports multiple frameworks.

Of course in js there's a Library for that: https://jsonforms.io/

Examples from the conversations of that time:

> ...we want closures to capture the values we rendered with, and to keep "seeing" those values forever. That's really important for concurrent mode where a notion of current value doesn't really exist. Hooks design models a component as being in many non-clashing states at the same time, instead of switching the "current" state (which is what classes model well). People don't really need to think about these details, but they're motivating the design a lot. [0]

> In Concurrent Mode, render may run more then one time, and since this in a class is mutable, renders that should be the same may not be. [1]

[0] - https://github.com/reactjs/rfcs/pull/68#issuecomment-4778866...

[1] - https://tkplaceholder.io/why-function-components-fit-react-b...

There are multiple names for this hook. You can find the documentation under the names useEvent or useEffectEvent.

-https://www.patterns.dev/ -https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md -https://dev.to/this-is-learning/qwik-the-post-modern-framework-3c5o -https://dev.to/this-is-learning/astro-framework-169m -https://developers.google.com/web/updates/2019/02/rendering-on-the-web -https://web.dev/vitals/

However, in React, function components can return a ReactNode. This type includes number | string | Iterable | undefined and will likely also include Promise( in the future.

I was also hoping that useEvent would eliminate some weird dependency cases, who knows when that will actually happen (https://github.com/reactjs/rfcs/pull/220).

Given a lot of unknowns on SSR and ReactEng working on RSC it feels like the wrong move to use next.js and I should just use normal react. For basic react is create react app the way to go or vite?

As mentioned before, Next.js takes a stance of treating every component as a Server Component by default. If you want to use a Client Component, you'll need to annotate the file with use client; directive at the top of the component file.

Use client is actually a React convention for what it’s worth. https://github.com/reactjs/rfcs/pull/227