Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor controllers mapping #120

Open
efraimgentil opened this issue Apr 30, 2015 · 1 comment
Open

Refactor controllers mapping #120

efraimgentil opened this issue Apr 30, 2015 · 1 comment

Comments

@efraimgentil
Copy link
Contributor

The controller mapping are scaterred all over the code and packages, maybe a good time to refactor and centralize the controller mapping and path mapping handling

Related #119

@efraimgentil
Copy link
Contributor Author

When when identifying the paths, we have the flux

  1. PackageScanner ( identify all controllers )
  2. ControllerScanner ( Find all methods with path annotations to each controller ) *
  3. ControllerMapping( Interete in each method and create the hte PathMapping )
  4. PathMapping ( is the map itself of the path ) **
  • -> Modify the controller path
    ** -> Modify the controllerPath and the method path

And we also have the CustomPathTemplate, that adds a "/" to the start of the path string

Is not a complex logic, but maybe only the PathMapping should handle the path moddifications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant