Prevent Area and Root controller name clashes #51
Milestone
Comments
Closed
artiomchi
added a commit
to artiomchi/R4MVC
that referenced
this issue
Jun 14, 2017
! Fixing view class reference for virtual controllers ! Fixing display/editor template registrations (also seems like I already did T4MVC#51 in previous commits)
|
Closed via #55. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the things that should be tackled is preventing the root controllers and area names from clashing.
Say a user has a
CatalogsController, and also aCatalogsarea with further controllers. The MVC class would have aMVC.Catalogsfield for the controller and aMVC.Catalogsproperty for the area.I've added a basic check for this, and will rename the area property in the MVC class to
MVC.CatalogsArea. All other areas (that don't clash) don't get the suffix.If someone has a
CatalogsAreaControlleror aCatalogsAreaarea this will of course cause a clash, but I'm not handling that, since there's no practical reason to have a controller or area named this way :)Does that sound reasonable?
(a patch to finish this logic will be in the next pull request late this week)
The text was updated successfully, but these errors were encountered: