This repository has been archived by the owner on May 6, 2018. It is now read-only.
Forward route matched params to router when generating URLs for generated resources #1
Labels
Milestone
Comments
lcobucci
added a commit
that referenced
this issue
Nov 16, 2017
In order to ensure that we have all required arguments when generating the route path (which is really usefull for sub-resource routes). Fixes: #1
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When working handling requests that creates items on subresources, like POST on
/authors/{author_id}/bookswhere the location header should be/authors/{author_id}/books/{id}.The text was updated successfully, but these errors were encountered: