react-json-form icon indicating copy to clipboard operation
react-json-form copied to clipboard

JSON editing made easy using form inputs.

Results 15 react-json-form issues
Sort by recently updated
recently updated
newest added

First of all, thanks for an awesome library. Are there any plans to support dynamic object properties defined with `patternProperties`? For instance, here is a basic example: ``` { "type":...

Following the suggestion from https://github.com/bhch/django-jsonform/issues/164 For context I have very little understanding of this codebase and very little knowledge in react I simply want op suggestion fixed

Using the last version of the lib available on npm, it seems to crash on "nested" schemas. For example, the "Array/List", "Referencing" or "Recursion" schemas from the Playground don't work,...

bug

I've started using your django-jsonform project, works wonderfully for our use case. One thing that's a little annoying: when adding a form input with type 'reset', the JSONField's input selectors...

bug
enhancement

**Features:** - [ ] Setting custom html class names on form elements - [ ] Providing custom text for button labels --- **Possible Solution:** Creating a new keyword called `ui`...

enhancement

Currently data input in the Playground is not editable. It will be useful to provide data for testing certain cases.

enhancement
playground

I have this following schema ``` { "type": "object", "properties": { "secret_code": { "oneOf": [ { "type": "integer", "title": "Numeric value" }, { "type": "string", "title": "String value" }, {...

bug

Currently, we're using indices for generating keys for array's children components. This may result in poor performance and also hinder optimization in child components. Related: #67

bug

Currently, the `errorMap` is not cleared when schema is changed on the validation tab. Line of concern: https://github.com/bhch/react-json-form/blob/v2.7.2/docs/src/tabs.js#L122

bug
playground

Currently, all the widgets fields are submitted with the form. But the expected behaviour is that only the JSON data is submitted. One possible solution is using `data-name` instead of...

bug