With this tool you can spend more time implementing the plugin's business logic in your favorite code editor rather than dealing with the more mundane tasks, like building forms or managing plugin versions. Here’s an example, instead of looking into the documentation for a list of supported form controls and their features, you can just open the Form Builder, find a suitable control in the Control Palette, add the control to the form and explore its properties with the visual inspector.īuilder implements a Rapid Application Development process that automates the boring activities without sacrificing complete control. With Builder you can create a fully functional plugin scaffold in a matter of minutes.īuilder makes the learning curve less steep by providing a visual interface that naturally incorporates Winter's design patterns and documentation. It shortens plugin development time by automating common development tasks and makes programming fun again. The Builder plugin works gracefully with your own work tools and methodologies, being both comprehensive and yet careful with its own scope of plugin modifications - allowing you to work on more complex plugin functionality in your own development environment without interference from the Builder plugin.īuilder is a visual development tool. Use simple, universal Builder components on your CMS templates to display full lists and single records. ![]() Manage your plugin's versions and migrations.Design and create your forms and lists.Define your plugin's Backend navigation items and available permissions.Define models for your database tables.Create and update your plugin's database schema, with automatic migration generation.I hope this might help someone looking for a similar answer.Composer require -dev winter/wn-builder-plugin Features The below represents the return of a (reusable) component (renderField) that is called from a form via a component= to the FormControlLabel to take the boolean from checked and set the value of value as a string of either "true" or "false". This is similar to what suggested in his post on. That said, I only needed to implement one line of code on the FormControlLabel element in order for the checked param to affect the value param, setting it to a string. ![]() If you want to set the default value of the checkbox to true, you can use initialValues, putting anything as a value for the checkbox, except boolean, false, as this will actually work as expected. In fact, anything put there in initial values will have the field thinking it's checked, except for the boolean, false, which you don't need as the default value is already false. value is controlled by checked), in that you cannot set the initial value of the checkbox field to "false" (using initialValues) and expect that checked will become false as a result. So it throws warnings when it receives a boolean.Īnother complicating-confusing may be a better word-factor is that (when a filed is of type=checkbox) this does not work the other way around (i.e. And Material UI is expecting (with props validation) on its FormControlLabel element value to be a string. ![]() I know this is an old closed thread, but Google kept sending me here as I was trying to find a solution of working with checkboxes, Redux Form, and Material UI.Īs I read the posts from I think he was suffering from the fact that (without touching anything) Redux Form will set the value of a checkbox field to the boolean of true when it is checked.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |