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.

Sign up for GitHub

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

Jump to bottom

Routing: Responder Classes #37

Open
5 of 7 tasks
smichaelsen opened this issue Nov 27, 2014 · 1 comment
Open
5 of 7 tasks

Routing: Responder Classes #37

smichaelsen opened this issue Nov 27, 2014 · 1 comment
Assignees
@smichaelsen
Labels
enhancement
Milestone
1.5

Comments

@smichaelsen
Copy link
Member

  • Make it possible to just provide a plain string responder in the routing array.
  • Define classes for the different responder types (Controller, Callable, Subrouting, String)
  • Introduce a factory that determines the responder type from the routing array and configures the object
  • The objects need to know how to dispatch them selfs, move that code away from the Dispatcher
  • Make it possible to define custom responder types via signal/slot
  • Make Subrouting work again
  • Cover all new classes with Unit Tests
@smichaelsen smichaelsen modified the milestones: 2.0, 1.4 Nov 27, 2014
@smichaelsen smichaelsen self-assigned this Dec 3, 2014
@smichaelsen
Copy link
Member Author

Possible source of inspiration: https://github.com/xperseguers/t3ext-routing

@smichaelsen smichaelsen modified the milestones: 1.4, 1.5 Dec 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smichaelsen smichaelsen

Labels
enhancement
Projects
None yet
Milestone
1.5
Development

No branches or pull requests
1 participant
@smichaelsen