Xcode scheme --work-dir path was hard coded

[mpclarkson]

Changed to: --work-dir=($SRCROOT) as it was hard coded to /Users/tanner...

I'm still having all sorts of problems getting anything to build on OSX using the SPM (at least without resorting to Docker) so I have to build using Xcode. This will make it easier for anyone else in my situation.

[mpclarkson]

I have added the ability to created nested resources. I have implemented this the same way as Laravel - namely using dot notation for the path - although this could also be achieved using the controller name.

The parameters are all snake_case for consistency but this can be easily changed. Just let me know what you prefer.

I'll write some tests for this tomorrow (it is night down here) but it works.

The new behaviour is:

Nested Resources

Route.resource("foo.bar", controller: FooBarController())
//Get foo/:foo_id/bar nil
//Post foo/:foo_id/bar nil
//Get foo/:foo_id/bar/:bar_id nil
//Put foo/:foo_id/bar/:bar_id nil
//Delete foo/:foo_id/bar/:bar_id nil

Single Resource
This remains the same -i.e. the trailing parameter is simply :id

Route.resource("foo", controller: FooController())
//Get foo nil
//Post foo nil
//Get foo/:id nil
//Put foo/:id nil
//Delete foo/:id nil

[tanner0101]

What is Zip2Sequence?

[tanner0101]

This looks great, but I will need to check it out on Mac / Linux and also write tests.

Anyway you could separate the workDir fix into a different PR that I could merge now?

[loganwright]

This won't run on linux for me, there'll need to be compatibility code.

[mpclarkson]

Cheers thanks. I'll update.

[mpclarkson]

Done. I have moved the nested resources into a separate branch and will submit a pull request later after I've written some tests.

[mpclarkson]

So this now only includes the --work-dir change

[tanner0101]

Perfect, thanks!