Nested resources -- How to?

[billyfordon]

Hi there,

This module is truly awesome!

I was wondering how to define nested resources like in Rails (http://guides.rubyonrails.org/routing.html#nested-resources)? Is that at all supported?

Thanks,

Billy

[teamon]

Thanks :)

You can use namespace for that but currently it's impossible to get the
same syntax as in rails.

Wys³ane z iPhone'a

Dnia 23 wrz 2012 o godz. 00:39 billyfordon notifications@github.com
napisa³(a):

Hi there,

This module is truly awesome!

I was wondering how to define nested resources like in Rails (
http://guides.rubyonrails.org/routing.html#nested-resources)? Is that at
all supported?

Thanks,

Billy

Reply to this email directly or view it on
GitHubhttps://github.com//issues/3.

[billyfordon]

OK. I guess getting the same syntax as Rails isn't important.

However, as far as I understood, namespaces are static. So how would I do this with say /magazines/:magazine_id/ads? I can see how to get a magazines namespace, but then I can't see how to connect this to a resource("ads", Ads).

[teamon]

I might find some time to make that possible but I can't promise anything.

Wysłane z iPhone'a

Dnia 23 wrz 2012 o godz. 00:47 billyfordon notifications@github.com
napisał(a):

OK. I guess getting the same syntax as Rails isn't important.

However, as far as I understood, namespaces are static. So how would I do
this with say /magazines/:magazine_id/ads? I can see how to get a magazines
namespace, but then I can't see how to connect this to a resource("ads",
Ads).

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/3#issuecomment-8793587.

[billyfordon]

OK. So right now it's not possible :)

I would be happy to help/test if necessary.

By the way, not sure if that would make it simpler, but it might make sense to limit nesting to one level, which is the advised rule of thumb for rails (http://weblog.jamisbuck.org/2007/2/5/nesting-resources).

[teamon]

Well, I'm actually a full time rails developer and from my experience
sometimes you really want more than one level.

If you could make a pull request with feature it would be awesome :)

Wysłane z iPhone'a

Dnia 23 wrz 2012 o godz. 01:00 billyfordon notifications@github.com
napisał(a):

OK. So right now it's not possible :)

I would be happy to help/test if necessary.

By the way, not sure if that would make it simpler, but it might make sense
to limit nesting to one level, which is the advised rule of thumb for rails
(http://weblog.jamisbuck.org/2007/2/5/nesting-resources).

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/3#issuecomment-8793675.

[teamon]

Syntax proposal:

trait Resource0[Id0] {
  def show(id:Id0): Handler
  // ...
}

trait Resource1[Id0, Id1] {
  def show(id0: Id0, id1: Id1): Handler
}

resource("posts", Posts){ // Posts must be Resource0
  resource("comments", Comments) // Comments must be Resource1

  collection {
    GET on "foo" to X // /posts/foo 
  }

  member {
    GET on "bar" to Y // /posts/:postId/bar
  }
}

with reverse routing support

val posts = new Resource("posts", Posts){
  val comments = new Resource("comments", Comments)
  val col = new Collection { 
    val foo = GET on "foo" to X 
  }
  val mem = new Member {
    val bar = GET on "bar" to Y
  }
}

The last one with new Collection and new Member is a bit ugly. Something much better could be achieved with 2.10 macros.