title: What's the AngularJS "way" of handling a CRUD resource
body: <p>I am interested in moving a lot of my client's "logic" away from Rails routing to AngularJS. I have slight confusion in one topic and that is linking. Now, I do understand there's more than one way to handle this, but what is the common practice in the AngularJS community for handling URLs on handling CRUD for resources. Imagine in the case of an athlete we have a URL such as the following to list all athletes:</p>
  
  <p><code>http://example.com/athletes</code></p>
  
  <p>To view an individual athlete:</p>
  
  <p><code>http://example.com/athletes/1</code></p>
  
  <p>To edit an individual athlete:</p>
  
  <p><code>http://example.com/athletes/1/edit</code></p>
  
  <p>To create a new athlete:</p>
  
  <p><code>http://example.com/athletes/new</code></p>
  
  <p>In AngularJS, is it common practice to reroute to similar URLs to create/edit/update? Would you just have one URL handle all of the CRUD type actions in one interface and never change the URL? If you were to change the URL, does that get handled via ng-click and in the click event would you use the <code>$location</code> object to change URLs? I'd love to be able to read up on common practices such as these, but having a difficult time in finding more recent literature on it in an AngularJS context.</p>
  
  <p>** NOTE **</p>
  
  <p>I totally get that you can still use RESTful routes to the backend in order to interact with server-side resources. My question is, what is the style that is recommended to use when updating URLs on the client-side. Are you using AngularJS to do that for each of the CRUD operations?</p>