Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I see this quite a bit with online apps. Lets take, for example, the following url:
https://github.com/account
For something like above, the route (in Rails 3) would look like:
get '/account', :to => 'users#edit', :as => 'account'
Or is there a better way to do this? Perhaps create its own Accounts controller? How would you go about this?
Probably instead of
it would be
With an edit button if the displayed user is the logged in one (like how github does it)
But yeah to me that seems like the easiest way to accomplish such a task