title: Spring Data Rest Frontend deep linking
body: <p>So i have been struggling with this one question some time now: </p>
  
  <p>How to handle details Page or deep linking on the Frontend. </p>
  
  <p>So, say, we got a paged collection endpoint with user entities in it and a React App consuming the endpoint.
  The flow would be, user authenticates, gets collections, clicks on an item and is either: </p>
  
  <ol>
  <li>Redirected to a new Url say: webapp.com/users/userid</li>
  <li>A modal opens with the user details.</li>
  </ol>
  
  <p>Say we got a scenario were two people working with the webapp, Person 1 wants to share a link with Person 2. Person 2 should do some updates on a specific user, which is identified by the link. 
  The link should be something like : <a href="https://www.webapp.com/users/" rel="nofollow noreferrer">https://www.webapp.com/users/</a>{slug or id} 
  With Option 2 this functionality is not mappable. 
  With Option 1 we got to expose the ids in the response to identify the resource, which may work, but we would still need to hardcode the url, as the findById method is not exported as a Uri Template. 
  So, my Solution would be to add a slug for the resources, implement a search method by the slug, and then get the user, if found, by its self-link. 
  Sounds like a good solution for me, but on the other hand, I would have to add an extra frontend id(the slug here) which would need to be also unique, to the database model.</p>
  
  <p>So how do you guys handle a problem like this, or is there anybody using spring data rest in this way or in production mode where you have the handle situations like this? </p>
  
  <p>Should mention that this isn’t a primary problem with spring data rest but rather with hateoas itself. </p>
  
  <p>thanks in advance 
  Florian</p>