Score Controller about golf_keeper HOT 1 CLOSED

while it is true that you need to remove a level of the nesting, in this case, you would not want to use shallow nesting feature in rails

The reason is - nobody should ever have the opportunity to change a player ID nor will they have the opportunity to view other players from what I gather. so there's no need to have the player resource involved in any nesting at all

this can be achieved in a number of ways, but one example would be using rounds:

The route for rounds should be at the top level and not nested under anything so the URL should simply be

/rounds

in the controller index action:

@rounds = current_user.rounds

The point is, you never need to pass around player IDs because it's always current_user and you have this variable already available in every view and action

The only caveat here is if you want the app to work in a way where players can see other player scores - then the rails shallow nesting option would work well

On Nov 7, 2014, at 3:48 PM, Kerry [email protected] wrote:

Create action is getting too nested bc of nested resources (player/id/round/id/score/id)

Need to fix routes with:

a) shallow nesting: http://nithinbekal.com/posts/rails-shallow-nesting/

b) replacing player w/ current_user

—
Reply to this email directly or view it on GitHub.

from golf_keeper.