Proposed solution to issue #224, getting the expected request_path when ...

...creating a nested resource

This solution follows along the lines of what you do with the parent id and includes the parent request path when building the resource.

Please give some feedback on this, if it's a fair solution, if something is missing. I would like your thought on this.