search

sumeetjain / outcomes-tracker

0 stars 0 forks source link

Should Entries be completely invisible to User (ie not used in public-facing routing)? #69

Open halfghaninne opened 8 years ago

halfghaninne commented 8 years ago

Right now, the route I go to to view a Job Application is /entries/:id, but the route I go to add a new one is /job_applications/new -- that's confusing right?

It's giving me a bit of a headache in thinking about how to add in routes and controller actions to add an Offer to an existing Entry (working on #53). Does that work go in the Entries controller? The Offers controller?

I can write it out and get it working, but I feel like I'm extending a bad organizational system (one that I set up this way...surely for a reason...surely).

sumeetjain commented 8 years ago

This is often a symptom of using scaffolds for everything. Controllers are supposed to map to experiences, but we often map them to models. It's fixable but not probably not a priority, so I think you were right to label it as technical debt.