Feature Request #3683
Exception naming conventions
| Status: | Feedback | Start date: | 02/02/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Kiall Mac Innes |
% Done: | 0% |
|
| Category: | Core | |||
| Target version: | Unscheduled | |||
| Resolution: | duplicate | Points: |
Description
As of KO 3.x all classes are suffixed (e.g. Controller_Template, Model_User or Database_Query).
Now there are Kohana_Kohana_Exception or Http_Exception_404.
Kohana_Kohana_Exception should be Kohana_Exception_Kohana while Kohana_ is the transparent extension prefix, and Exception_Kohana is the specific class type.
I would rename all http exceptions to Exception_Http_X, or is the actual form used for grouping them together?
Related issues
History
Updated by Kiall Mac Innes about 1 year ago
- Status changed from New to Closed
- Assignee set to Kiall Mac Innes
- Resolution set to duplicate
Meriging with #3765
Updated by David Pommer 3 months ago
- Status changed from Closed to Feedback
- Target version changed from v3.2.0 to Unscheduled
Sorry for bumping this again, but this seems not to be a duplicate of #3765.
The sugestion there is to use the transparent extension (e.g. View_Exception) instead of the core classes (Kohana_View_Exception).
My purpose is to know if it's intended having classes like Http_Exception_404 (grouping the http stuff together) instead of Exception_Http_404 (grouping exceptions themselves).