#829: Throw out legacy naming scheme support for Actions, Views and Models
---------------------+------------------------------------------------------
Reporter: david | Owner: felix
Type: task | Status: new
Priority: high | Milestone: 1.0
Component: _OTHER_ | Version:
Severity: blocker | Keywords:
Has_patch: 0 |
---------------------+------------------------------------------------------
Currently, an Action in
''{{{%core.app_dir%}}}''{{{/modules/Foo/actions/Bar/BazAction.class.php}}}
can have the following class names:
* {{{Foo_Bar_BazAction}}} (fully qualified)
* {{{Foo_BazAction}}} (eww)
* {{{Bar_BazAction}}} (module missing)
* {{{BazAction}}} (eww)
Views and Models are similar, although Models do not (yet, #631) support
nesting.
This causes a lot of ambiguity and, among others, prevents us from
enabling the following things:
* autoloading for Actions, Views and Models
* unproblematic unit testing with mocked Actions etc
* renaming etc of Actions, Views and Models using the build system
As feedback regarding this on the mailing list was unanimously positive,
we'll do this before 1.0, so it doesn't bite us down the road.
--
Ticket URL: <http://trac.agavi.org/ticket/829>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
