to nest nest?


premise:
usually during certification new flush rails app, i pull out models family per user navigations. wholly i strike place where i need ask myself, presumably i should over common "rule thumb" nesting some-more 1 turn deep. infrequently i feel need nest, rather formulating another namespace lane duplicating work.

here's an example:



models: user, company, plcae

user belongs companies (many many)

user belongs locations (many many)

company belongs locations (many many)



routes:

1 turn nesting

users/:user_id/companies/ - list companies associated user

users/:user_id/locations/ - list locations associated user

more 1 turn nesting

users/:user_id/companies/:company_id/locations/ - list company-locations user



so, doubt presumably suitable nest some-more 1 turn low ror? approbation no? why?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?