Explore >> Select a destination
|
You are here 
|
www.integralist.co.uk | ||
| | | | |
konradreiche.com
|
|
| | | | | Ruby on Rails applications are modelled around active record yet what if your application is based on a domain which needs to be provided in a programmatic way? In other words, your application, controller and views stand on a fixed set of Ruby classes yielding the context. In a manual fashion one would implement this by creating controller and views for each specific class. Assuming that the classes of this domain share the same interface this approach would introduce a lot of redundancy. With meta-programming this amount can be cut down. | |
| | | | |
github.com
|
|
| | | | | Ruby on Rails. Contribute to rails/rails development by creating an account on GitHub. | |
| | | | |
codefol.io
|
|
| | | | | [AI summary] This article discusses best practices for organizing code in a Rails application, focusing on models, controllers, views, helpers, the /lib directory, and gems to avoid code duplication and maintainability issues. | |
| | | | |
www.github.com
|
|
| | | my blog, with astro. Contribute to Krayorn/blog development by creating an account on GitHub. | ||
