0.1.3 — form editor options fix

Fixed

• Form field editors now accept the editor widget's public option names. A FieldItem's editor_options are documented as the editor widget's keyword arguments, but the form built the internal widgets and forwarded the options unchanged — so the public names raised an error (editor_options={"step": 10} on a numberfield failed with unknown option "-step"; only the internal increment worked), and the textarea editor could not accept show_border at all. Editors are now built from their public widgets, so step, min_value / max_value, show_steppers, show_border, mask, and the slider bounds all work as documented — in Form, FormDialog, and the DataTable add/edit dialog. This also fixes two latent textarea bugs, where a programmatically set value and required validation were ignored. (#353, #354)

What's Changed

• Set up GitHub Discussions routing and templates by @israel-dryer in #346
• Fix splash progress docs example by @israel-dryer in #348
• fix(form): editor_options use public widget kwargs (#353) by @israel-dryer in #354

Full Changelog: v0.1.2...v0.1.3