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

WebDispatcher throws exceptions #119

Closed
ValentinTrinque opened this issue May 27, 2014 · 1 comment
Closed

WebDispatcher throws exceptions #119

ValentinTrinque opened this issue May 27, 2014 · 1 comment

Comments

@ValentinTrinque
Copy link
Member

Due to the WebDispatcher behavior, Beluga core raises exceptions:

From the documentation:

In case the corresponding method doXXXX is not found on the api object, or if the URL is /, the action doDefault is used instead. An exception DispatchError.DENotFound("XXXX") is thrown if there is no default action (XXXX here being the placeholder for the URL part name).

In case the required part is missing, an exception DispatchError.DEMissing is thrown. In case the required part does not have the valid format, an exception DispatchError.DEInvalidValue is thrown.

The problem is we should allow the user to set his/her callback to manage this error by him/herself, especially for DEMissing because this is something which should be handled inside module and not the core by catching these exceptions.

@brissa-a
Copy link
Contributor

Same topic as #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

2 participants