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

Core errors #116

Closed
Masadow opened this issue May 19, 2014 · 2 comments
Closed

Core errors #116

Masadow opened this issue May 19, 2014 · 2 comments

Comments

@Masadow
Copy link
Member

Masadow commented May 19, 2014

I'm not sure it's enough to send an exception when an error occured within the core. I mean some are mandatory, but the database connexion, dispatcher not found or whatever could lead to a custom page.

For instance a class like

class ErrorView
{
    public function new() {
        /* ... */
    }

    public function databaseError() {
         render("beluga_error_database.mtt");
    }

    public function dispatchError() {
        render("beluga_error_dispatch.mtt");
    }
}

The end user would just have to override this class to implements its own error pages.

What do you think ?

@ValentinTrinque
Copy link
Member

I agree to say that exceptions shouldn't handle this kind of errors. So I will definitely go for another system to manage errors.

The idea is interesting though.

@brissa-a
Copy link
Contributor

Outdated, see #182.

@HaxeBeluga HaxeBeluga locked and limited conversation to collaborators Sep 12, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants