formily VS react-jsonschema-form

GitHub https://github.com/alibaba/formily GitHub Star 10.9k The most recent update on GitHub Five months ago Official website https://formilyjs.org/ Documentation https://formilyjs.org/guide

Enter Formily, by Alibaba which does exactly the above. With a JSON schema, forms can be generated whilst keeping control of the data model.

Even though it’s quite amusing, this is an edge case that we’d likely need to support if aiming for production use. The most common approaches are to add more validations and retries to our application’s code, improve the prompt to direct GPT, or try different temperatures of the model. ## **Use case - build dynamic forms in React** Another common use case that we can try to automate is building custom forms dynamically. Many applications, such as surveys, custom forms etc., rely on this feature to gain feedback from its candidates, customers or potential leads. GPT makes it incredibly easy to build a tool that allows a regular user to create such a form by providing natural language input. Let’s use a library called [react-jsonschema-form](https://rjsf-team.github.io/react-jsonschema-form/docs/). It’s a React-based library that generates forms based on a JSON definition. It also contains an extensive schema definition that such JSONs can be validated against. We can leverage the fact that GPT was trained on a large dataset that also includes definitions of commonly used JSON schemas. That means we don’t have to provide the exact schema, and we can refer to it in our prompt by name. Let’s create a prompt that: 1. Specifies that we would like to use the schema of react-jsonschema-form 2. Include the user's definition of the ideal form 3. Will specify some additional criteria for the output (i.e. make sure that we only get a JSON as a response)

Thanks for your feedback !

It does not rely on JSON schema at all, the idea was to build a representation that binds together data structure, views and behavior in a self-contained way (like .xlsx does).

There are a few tools that do enable to link JSON schema to views, like react-jsonschema-form (https://rjsf-team.github.io/react-jsonschema-form/) but you need to manage them separately, and they usually do not propose a way to add the fields "methods" (which was the feature I found interesting to make "dynamic" spreadsheets).

That being said, I think the framework should clearly propose an export from Schema to JSON Schema or Yaml at some point, just as you should be able to start building your Schema by importing a JSON Schema (and although there might be some gray zones between the 2).

No, sorry, it's not yet open-source, and currently there are some strong links between Document and Workspace (Links, Files...) that would need to be more "abstracted" to make the builder an independent component. But I hear you point ! (and all the comments in this thread are raising the same ! :) )

I've been very passionate about a project called react-jsonschema-form (github, editor). I personally hate writing forms, and love the idea of serializable components, schema, validation all in one. I've always wanted an alternative to this project that offered an alternative to react, and possibly the ability to render a schema form to static HTML (like ssg).

See their playground app for examples of creating schema driven forms in no time.

I've tried with https://github.com/rjsf-team/react-jsonschema-form ,but the performance is poor when dealing with deep nested form with many inputs.

For example, I had a requirement for my team recently to be able to build dynamic form UIs, based off a JSON schema. There are heaps of javscript frameworks for this task e.g. react-jsonschema-form, but nothing in nuget or Blazor is going to help there. So you'd have to write all the logic yourself.

React-json-schema form has plenty of tests, using... it looks like react-dom/test-utils

https://github.com/rjsf-team/react-jsonschema-form

YAML-LD (application/ld+yaml) round-trips to JSON-LD (application/ld+json) which round trips to RDF; so W3C Linked Data Signatures / W3C Verified Claims cryptographic signatures verify regardless of graph representation.

YAML-LD > 3.1 JSON vs YAML comparison: https://json-ld.github.io/yaml-ld/spec/#json-vs-yaml

React Json Schema Form: https://github.com/rjsf-team/react-jsonschema-form