3 ms·
That's all fine and dandy until you change a class name, method name, parameter name. Way to expose internal details about your implementation, though.
by stouset 15y ago
That's all fine and dandy until you change a class name, method name, parameter name.
Way to expose internal details about your implementation, though.
- romaniv 15y agoIn practice, this is a non-issue. Instead of thinking of your routers as "the interface" and your controllers as "implementation" you can think of the controllers as the interface and everything else as "implementation". If you're concerned about arbitrarily changing class and methods names that are only used as interaction points for the user, you should be similarly concerned about arbitrarily changing routing logic.
- stouset 15y agoSo instead of having a router and controllers, you're just making the controllers do the work of the routers too. I mean, you can, but why would you?