v0.26.0

• Fixed #147: Revisited async rendering strategy, improved performances and UI reactivity (#153)
• Fixed #142, merged #148: Added DateWidget along DateTimeWidget, added buttons to set current date/time and to reset field values.

v0.25.0

• Merged #132: Handle fixed items arrays (@rhgb)
• Fixed #140: Schema $ref now always overrides local schema type; also ensures local defaults will take precedence over referenced ones.

v0.24.0

Fixes #137: Optional fields shouldn't always enforce a value.

Previously default values where assigned to state for every field type by default, even if their schema wasn't defining one and the user has had no interaction with widgets yet.

Now the field value remains undefined until there's end user interaction with its widget(s).

v0.23.2

• Fixed #135: Playground's schema editor doesn't render. (#136)
• Fixes #130: Live validation not fully disabled by default. (#138)
• Object field description is now rendered in a paragraph.

v0.23.1

• Merged #131: Upgraded React to v15.0.1.

v0.23.0

• Fixes #122: Better default DateTimeWidget:

v0.22.0

• Fixes #109: Avoid tabbing to the delete and add buttons in ArrayField.
• Fixes #43: Added support for hidden widgets.
• Fixes #114: Added a widget for the date-time string format.
• Fixes #113: Added support for email and uri string formats.
• Fixes #119: Do not render two equivalent labels for checkboxes.
• Fixes #115: Added ui:help uiSchema directive.
• Fixes #117: Imroved docs for Form event handlers.

v0.21.1

• Merged #106: Fixed bug with nested arrays: "Add" button didn't work for outer array.
• Merged #107: Added missing default props for SchemaField to make defining a custom one easier.

v0.21.0

• Merged #102: Make live form validation an option, which is now false by default. If you plan on keeping the previous behaviour, pass the liveValidate prop as true to the Form component.

v0.20.0

• Merged #100: Switched to use Bootstrap semantics

The library now generates Bootstrap semantics by default, so one can use it along themes to have decent looks for their forms.

From the updated docs:

Styling your forms

This library renders form fields and widgets leveraging the Bootstrap semantics. That means your forms will be beautiful by default if you're loading its stylesheet in your page.

You're not necessarily forced to use Bootstrap; while it uses its semantics, it also provides a bunch of other class names so you can bring new styles or override default ones quite easily in your own personalized stylesheet. That's just HTML after all :)

If you're okay with using styles from the Bootstrap ecosystem though, then the good news is that you have access to many themes for it, which are compatible with our generated forms!

Here are some examples from the playground, using some of the Bootswatch free themes:

Last, if you really really want to override the semantics generated by the lib, you can always create and use your own custom widget, field and/or schema field components.