Left in the wrong place, sorry.

Because 0 is falsy, the default value is ignored and null is used.

Related: bhch/django-jsonform#45

Instead, let the users set any variables they want. And keep them in a container object like extraConfig:

<ReactJSONForm
    editorState={...}
    onChange={...}
    extraConfig={{
        modelName: ...
        fieldName: ...
    }}
/>

See bhch/django-jsonform#31.

Initial blank data is not being set for numbers and boolean (and possibly others). This leads to this error:

Warning: A component is changing an uncontrolled input to be controlled.
This is likely caused by the value changing from undefined to a defined value, which should not happen.
Decide between using a controlled or uncontrolled input element for the lifetime of the component.

If a select input is of type boolean or number, then if an option has a falsy value (false or 0), then selecting that option doesn't display that options as selected in the select box.

However, the value in the data is correctly reflected.

And if the initial data is not provided, there's this error:

A component is changing an uncontrolled input to be controlled

Related: bhch/django-jsonform#46

Related: bhch/django-jsonform#48

An autocomplete widget such that when a user types in it, it will send AJAX request to the server to retrieve choices dynamically.

When the json form renders, it automatically adds default form fields to match the schema. This also adds those items in the underlying form data.

If the form data is initially empty, and the form is unedited, the submitted value of the form should match the initial state.

See: bhch/django-jsonform#38

HTML (or browsers?) always returns a string value from an input. However, this library should convert the type as per the type keyword.

For example, something like this should return a boolean value:

{
    type: 'boolean',
    choices: [
        {label: 'Yes', value: true},
        {label: 'No', value: false},
    ]
}

This seems to work properly for number type: even though the browser returns a string, the values are converted to number.

If the values are anything other than string, then it doesn't work.

See: bhch/django-jsonform#54

See: bhch/django-jsonform#40

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 name on inputs.

For supplying custom display label for a choice, the keyword should be title instead of label to stay consistent with the schema spec since everywhere else, title is used to control the label of an input field as well.

See: bhch/django-jsonform#12

See bhch/django-jsonform#19

See: bhch/django-jsonform#9

Once the FormDateTimeInput component mounts, it starts listening for all click events. This is to close the time selector popup when a user clicks outside. But this also listens for click events even when the time selector is hidden. This seems bad for performance.

The component should only listen for click events while the time selector is visible/mounted. The solution is to move the click event listening code down to the time selector popup.

It should a number.

Example schema:

{
    type: 'array',
    items: {
        type: 'array', // directly nested array
        items: {
            type: 'string'
        }
    }
}

Currently datetime format is support, however the Standard JSON Schema spec has date-time.

So, add support for date-time and make datetime an alias.

First of all, thank you for the library, it is really helpful.

I am trying to upload a file following your tutorial in the documentation. However, I am facing an error of Permission Denied due to missing CSRF token.

I am using the JSONField in django's admin changeform. While going through your code, I noticed that you are retrieving the CSRF token from cookie as stated here. However, in admin changeform or while using the middleware django.middleware.csrf.CsrfViewMiddleware a hidden HTML field with name csrfmiddleware is added and no csrftoken token is set in the cookie.

As a workaround, I have set the cookie manually in my js file:

document.cookie = "csrftoken=" + $("input[name=csrfmiddlewaretoken]").val()

Then everything works as expected.

To resolve this I propose to modify getCsrfCookie function to check for the csrfmiddleware field or cookie before returning null.

Disable the move buttons instead of hiding them.
See bhch/django-jsonform#33.

The values are being changed in the data, however, the widget inputs still show old values.

Implement referencing using the $ref keyword. This would also allow recursive nesting.

Booleans should be null by default.

Also, if the default value is explicitly set to null, it is not respected and set to false.

Array

• uniqueItems

String

• minLength
• maxLength
• required

Number / Integer

• minimum
• maximum
• exclusiveMinimum
• exclusiveMaximum
• multipleOf
• required

Boolean

• required

See bhch/django-jsonform#25

See bhch/django-jsonform#35.

FormInstance's data is only updated in the onChange method. But the initial data (which is returned after syncing the data with schema) is not sent to FormInstance. Hence, calling getData() returns stale data.

Example:

var form = reactJsonForm.getFormInstance(...);

form.getData(); // -> returns stale/unsynced data if a change event hasn't occurred yet

Open a modal when user wants to select a file and request existing files from the server.

See bhch/django-jsonform#36.

So that it can be used outside of django admin.

i.e. the value of hour input should go down from 0 to 12 and go up from 12 to 0. Same for minutes and seconds, (0 to 59 ...).

See: bhch/django-jsonform#20

Since the upload of the file is done through Ajax call to an endpoint specified in Django settings.JSONFORM_UPLOAD_HANDLER, then there might be a case where the client would upload and close the page or cancel saving the model and the files would be still be uploaded without any link to a record in the database. In this case, how would you remove these uploaded files.

Proposal:

One way I can think of, is when a file is successfully uploaded, then in the .then((result) we store the returned file name in a list in react, and upon exit of page without saving (like explained here), if the list is not empty, then we send a DELETE to settings.JSONFORM_UPLOAD_HANDLER to delete those files. The clear button should as well send DELETE.

In this case, the handler endpoint should deal with both POST and DELETE methods.

Maybe rjf-label-required.

That way it becomes easy to share a particular demo.

bhch/django-jsonform#29