routeresolver - n number of controllers
tonyeung opened this issue · 3 comments
The way the routeresolver is written right now, all the controllers have to be in one folder. If we want to differentiate between sections or areas, we would need to modify the resolver. We are considering adding a path parameter to handle folders. What is your opinion on this?
I think that makes a lot of sense for large apps where you have areas with controllers in them. I think you’d almost have to introduce some type of new property into the routing to account for that.
Dan
From: tonyeung [mailto:notifications@github.com]
Sent: Friday, June 14, 2013 11:44 AM
To: DanWahlin/CustomerManager
Subject: [CustomerManager] routeresolver - n number of controllers (#3)
The way the routeresolver is written right now, all the controllers have to be in one folder. If we want to differentiate between sections or areas, we would need to modify the resolver. We are considering adding a path parameter to handle folders. What is your opinion on this?
—
Reply to this email directly or view it on GitHub #3 . https://github.com/notifications/beacon/-qe5h4jddzcHcmhqXzVhY06qWwttgZQNtf-QuDlwiUV7Ca5-A3tb03bIWXJ3S3mD.gif
Thanks Dan. We will go ahead and do that. Do you want me to create a pull so you can integrate?
Sure – that’d be great!
Dan
From: tonyeung [mailto:notifications@github.com]
Sent: Friday, June 14, 2013 12:52 PM
To: DanWahlin/CustomerManager
Cc: Dan Wahlin
Subject: Re: [CustomerManager] routeresolver - n number of controllers (#3)
Thanks Dan. We will go ahead and do that. Do you want me to create a pull so you can integrate?
—
Reply to this email directly or view it on GitHub #3 (comment) . https://github.com/notifications/beacon/-qe5h4jddzcHcmhqXzVhY06qWwttgZQNtf-QuDlwiUV7Ca5-A3tb03bIWXJ3S3mD.gif