4 ms·
When it comes to traditional web frameworks, the most important part is handling regular HTML forms. Reason being, a form is the only native mechanism your cust
by andreygrehov 4y ago
When it comes to traditional web frameworks, the most important part is handling regular HTML forms. Reason being, a form is the only native mechanism your customers have to use to interact with your service. Forms are important. Specifically, validation and error handling. I think Laravel does it really well. It's been a while, but Laravel has a wrapper around HTML forms. This wrapper does everything you need: server-side form validation, form generation, flexible error handling that takes care of client error messages, placeholders, input values, css classes for invalid states, you name it.
Does Pushup help engineers with HTML forms?
- miohtama 4y agoThis plus CRUD pattern - after the submission you want to edit the data usually with a slightly different form.
- randomguy0 4y agoAny more info on this form wrapper for Laravel?
- andreygrehov 4y agoThis is how it used to be - https://laravel.com/docs/4.2/html https://laravel.com/docs/4.2/html I haven't used Laravel for many years. I couldn't find the equivalent functionality in the latest version of the framework, which is 9.x, but pretty sure they should have something similar.
- AlbinoDrought 4y agoHere's the latest equivalent of those docs: https://laravel.com/docs/9.x/blade#forms https://laravel.com/docs/9.x/blade#forms
- chx 4y agoRegular HTML forms are hard. Source: I was the Drupal form API maintainer for a long time. Way too long.
- paulsmith 4y agoNot yet, but that is the intent. As a long-time Django user I have a high bar for the kind of forms support a framework should provide. One of my thoughts/beliefs is that, as a compiler with complete control over the page, there is a lot Pushup can do on both the markup generation side as well as checks and validations. eg., automatic CSRF token insertion, compiler "warnings" for accessibility, etc.