ActiveModel Form Objects

Explain why it's better to use Plain Old Ruby Objects (POROs) to move business logic away from Ruby on Rails controllers. But it also shows how to use the best of ActiveRecord by using the ActiveModel to extend POROs.

Transcript

1. ActiveModel Form Objects Olivier Robert March 19th, 2018
2. Intro • PORO managing complex controller flow: ◦ Lots of validation logic ◦ Creation of multiple models • Use ActiveRecord validations in the form object class: ◦ Handle data validation errors in the form ◦ Use ActiveModel naming conventions for generating form endpoints e.g. save(!), update(!), create(!)
3. How To: Setup Store form objects in a separate sub-directory
4. How To: Setup Includes the module ActiveModel::Model
5. How To: Validations 1. Use ActiveModel validations just like in models
6. How To: Validations 2. Create a custom Validator
7. How To: Validations Append errors to the errors attribute
8. How To: Persistence Wrap ActiveRecord methods inside a transaction
9. Keep business logic out of the Controller and Views
10. Enhance PORO with built-in functionality in Ruby on Rails
11. Thanks! Contact Nimbl3 hello@nimbl3.com 399 Sukhumvit Road, Interchange 21 Klongtoey nua, Wattana Bangkok 10110 20th Floor, Central Tower 28 Queen's Road Central, Hong Kong nimbl3.com