mirror of
https://github.com/TracksApp/tracks.git
synced 2025-12-25 03:30:13 +01:00
This may be a bit extreme. It's modeled after the ideal "rails way". In the controller, we now know the name of a single resource. It doesn't happen to be backed by a database table, but it does know all about the task of collecting stats, leaving the controller concerned with just munging params and rendering stuff. I called the resource `IndexPage`, to avoid the temptation of trying to reuse it, which can get pretty messy. Later, if a better abstraction appears, it should be fairly painless to alter. |
||
|---|---|---|
| .. | ||
| contexts | ||
| data | ||
| feedlist | ||
| integrations | ||
| layouts | ||
| login | ||
| notes | ||
| preferences | ||
| projects | ||
| recurring_todos | ||
| search | ||
| shared | ||
| sidebar | ||
| stats | ||
| todos | ||
| users | ||