JSONForms
use-context-selector
JSONForms | use-context-selector | |
---|---|---|
21 | 27 | |
1,953 | 2,473 | |
2.7% | - | |
8.8 | 6.5 | |
14 days ago | 6 days ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
JSONForms
-
Looking for an Android framework for dynamic form creation based on JSON schema
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.
- How do you handle very big forms?
-
What is the best practices for creating multi-step form?
We use JsonForms and for multiple forms and its quite powerful & consistant
-
What would make you use (or not) a tool like JSON Forms for your apps? I'm asking cause I want to learn how to evaluate tooling
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.
-
Server Sent UI Schema Driven UIs
Json Forms: https://jsonforms.io/
- JSONForms
-
Form builder based on data structure
Yes, exactly. I did some searching after I posed the question and found this so far https://jsonforms.io/
-
What are your struggles when working with forms in react ?
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.
-
RJSF : My Favorite (Underrated) React Form Library
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.
-
CRUD with dynamic database, what is the best practice?
Of course in js there's a Library for that: https://jsonforms.io/
use-context-selector
-
Having too many contexts - is it a problem?
Use jotai, or as someone else mentioned, zustand. React Context out of the box requires a very deliberate mental model due to a lack of tooling around selecting slices of state. This is why packages like react-context-selector exist: https://github.com/dai-shi/use-context-selector
-
Truly the best time to be a cs student
Unless I've missed it, context doesn't have selector IIRC. You'd have to use a third party solution useContextSelector
-
use-next-context: Performance-optimized React Context API.
How does this differ from https://github.com/dai-shi/use-context-selector?
-
Tips for managing and organizing complex state with React context
you can always split out context state or use a library to help with rerender issues like https://github.com/dai-shi/use-context-selector, or just switch to jotai or something else if you want something more ergonomic or better design patterns.
-
ReactJs - Useless re-renders when a context changes - HOW TO SOLVE IT ?
If you don't want to swap out useContext, you could always use useContextSelector, which helps you limit what props in the context should rerender the component.
-
React I Love You, But You're Bringing Me Down
I wouldn't call this easy
-
is Redux the first state management library you'll advise beginners to learn these days?
It wouldn't be clear to anyone learning Context API either. At least, not using official docs. Because Context API is not supposed for state management, and if you for some unknown reasons try to roll your own state management on top of it, you have to use tricky libraries to work around the issues resulting from such abuse.
-
What are some React Tricks/Tips for React Devs?
Any time anything in the context changes, any component that is consuming it will re-render. If you use it for frequently changed values, this library is needed to reduce unnecessary re-renders.
-
Surprising Performance Lessons from React Microfrontends in Production
Use of this implementation of useContextSelector
-
Inflist, an experiment using PureScript and React
Another technology I use regularly is Redux. But this time I wanted to manage the global state in a simpler and clearer way just using React hooks. I decided to go with a simple useReducer combined with theuseContextSelector hook which will avoid the whole applicationโs re-render caused by the native useContext hook.
What are some alternatives?
react-jsonschema-form - A React component for building Web forms from JSON Schema.
zustand - ๐ป Bear necessities for state management in React
formik - Build forms in React, without the tears ๐ญ [Moved to: https://github.com/jaredpalmer/formik]
reselect - Selector library for Redux
react-hook-form - ๐ React Hooks for form state management and validation (Web + React Native)
Next.js - The React Framework
formily - ๐ฑ๐ ๐งฉ Cross Device & High Performance Normal Form/Dynamic(JSON Schema) Form/Form Builder -- Support React/React Native/Vue 2/Vue 3
react-tracked - State usage tracking with Proxies. Optimize re-renders for useState/useReducer, React Redux, Zustand and others.
ngx-formly - ๐ JSON powered / Dynamic forms for Angular
react-final-form - ๐ High performance subscription-based form state management for React
why-did-you-render - why-did-you-render by Welldone Software monkey patches React to notify you about potentially avoidable re-renders. (Works with React Native as well.)