| ** How can you link within templates to other acti | | ** How can you link within templates to other acti |
| ons/views/... ? ** | | ons/views/... ? ** |
| | | |
| there is a link_to template function which gets pa | | there is a link_to template function which gets pa |
| ssed a controller, action and optionally id. (ie. | | ssed a controller, action and optionally id. (ie. |
| the params which are defined in the route) | | the params which are defined in the route) |
| | | |
| # Various Comments | | # Various Comments |
| t | | t |
|
| | | ## DRY
|
| | |
|
| | | Don't Repeat Yourself !!! and i also apply this to |
| | | frameworks - they shouldn't repeat themselves ! j |
| | | ust because stuff is generated by scripts, doesn't |
| | | mean it is not there.. if it is the same for all |
| | | applications, why not just put it into a generic b |
| | | ase class, instead of copying it to every controll |
| | | er/template/.. ?
|
| | |
|
| | | And why does every documentation say 'create this |
| | | line in both create and update' - this has to stop |
| | | ! i want to accomplish one single task, why do i |
| | | have to add the same line of code to two different |
| | | methods ?
|
| | | |
| # Code Examples | | # Code Examples |
| | | |
| ## Migration file | | ## Migration file |
| | | |
